I would like to emphasize that there is not always possible to replace a PL/SQL event action with a Workflow. If you have complex things/things in business critical flows/things in performance critical flows in PL/SQL it might be impossible or not suitable to do that in a Workflow. From documentation: “This will require analysis to determine which can be replaced using another approach such as a Workflow, Extend on the Outside or Extend on the Inside; and which can be removed, perhaps because new features in IFS Cloud render them redundant.” https://docs.ifs.com/techdocs/23r1/040_tailoring/225_configuration/150_config_best_practice/#best_practices_for_custom_events Hi Tomas,It’s true, it’s not always possible to replace SQL event actions with a Workflow. Nor, given the nearly unlimited flexibility of SQL event actions, will it every likely be. However, there are costs to those SQL event actions such as:There’s no guarentee they will work from release to release. Underlying schema cha
One of the problems is that IFS presumes that their business rules and validations are 100% useful for every customer. Having some flexibility or adaptability or yes in some cases, the ability to bypass them is entirely necessary to run a business efficiently. In many instances, there are cumbersome tasks or routes to finish the transaction that causes problems for users to the point they either aren’t doing them right or just don’t do them. Executing SQL event actions becomes a very necessary transaction even as mature as V9 was, let alone with Cloud where all of the tools were stripped out. Hi Shawn,Thanks for the insight. Data quality and management is critical for IFS Cloud and ensuring the value of new and existing features we bring to our customers. It’s imperative today that data be in a state expected by the system, and critical to where we’re going with BI & analytics as well as AI and Machine Learning. Can you give me some examples of use cases you believe you need SQ
We have no plans to deprecate online SQL event actions through at least 2024. However, for new implementations, we recommend Workflow instead. For upgrades, where feasible, we recommend replacing online SQL event actions with Workflows.Why Workflows?Online SQL presents many problems. If we were to build IFS Cloud, from scratch today, there's no way we'd consider a feature like this. It's insecure and problematic to our evergreen ambition. It requires extensive knowledge of our schema, and can bypass our business rules and validations.Workflows address these problems, and enable customers to optimize the system themselves.Why Now?23R2 represents a great leap forward for Workflows. In the past, our APIs severely limited the use cases we could support. In 23R2 however, we've enabled the new Entity Service APIs. Where most of our previous APIs were obtuse and procedural, the Entity Service APIs are transparent and granular. With them, you can orchestrate transactions in the same way onlin
Yes, it is no longer supported.
Hi @jporter ,We’ve made a lot of investments in the DMM across 22R2 and 23R1. In 23R1, we’ve significantly improve performance, added the ability to fetch data in the pre-deployment process (which helps with key resolution, calculating values, and defaulting data based on complex logic).We’ve got investments planned for the DMM in our roadmap over the next few years. Those include things like concatinating data from multiple source columns, enforcing and validating case, validating migration data against data in the target environment, and scheduled migration jobs, just as an example. The DMM IS our tool of choice for migrations, and where all of our new feature investments will be made.When we’re able to, we’ll look to deprecate the Data Migration Tool. There are a few use cases it uniquely supports, so we won’t deprecate it this year, but we intend to get down to one product.I’m not an expert on the Migration Toolkit. However, Eric Heinze is the product manager for our migration tool
As Jens states, while we currently support both the Data Migration Manager and the older Data Migration Tool, we strongly recommend customers and partners use the Data Migration Manager. Other than corrections, no further investment is going to be made in the legacy Data Migration Tool. Conversely, we’re investing heavily in ensuring that the Data Migration Manager offers an optimal experience for migration projects.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.
