“IFS Failure Event”s are used to signal that an error condition has been meet, the transaction should be rolled back and a user message explaining the validation error displayed to the user. The word “Event” is a bit confusing in this instance because it’s not refering to an IFS Event, but rather a specialization of a BPMN End Event.Docs can be found here: https://docs.ifs.com/techdocs/22r1/040_tailoring/500_business_process_automation/050_business_process_modeling/040_ifs_failure_event/
BPA isn’t really supported for any of the mobile solutions because the of the mobile solution architecture when Workflows were built. You can use Asynchronous Event based Workflows (Process Enrichment). Configuration using SQL is basically the old SQL Events. There aren’t many details in the docs below, but it basically generates a database trigger with the code provided.https://docs.ifs.com/techdocs/22r2/040_tailoring/225_configuration/010_config_best_practice/#what_are_custom_eventsAuthoring a SQL event without database access can be challenging because it’s helpful to see the code structures (the API explorer doesn’t help much here). Depending on your deployment model, getting access might be a challenge.
Hi,Thank-you for your interest in using a workflow to customize your process. Unfortunately, MWO only supports Asynchronous workflows at this time. As a result, you are unable to perform validation or user tasks because the initial request will have already been committed to the database when the asynchronous Workflow is executed.There are not any alternatives using Workflows in MWO, however classic customization and configuration tools making use of SQL are available in these cases.
@MiLeNL is correct, Events only support automations, user interactions are no longer supported.However, Workflows do include support for User Tasks when reacting to a Projection (API) call. When these workflows are executed, each User Task is translated into a modal dialog in IFS Cloud providing a consistent user experience.https://docs.ifs.com/techdocs/22r2/040_tailoring/500_business_process_automation/040_workflow_tooling/
Hi Theo,This is a known issue. Some progress has been made in 22R2 (read was specifically targetted) however complete support for nested collections (function calls, bound actions) haven’t been implemented yet.
The mechanism for determining which Projection to invoke from within Aurena is a bit more involved.The models (client, projection and entity) are transformed and stored within the database in an intermediate format, then translated again in some customized services generating Aurena specific metadata that contains the minimal linkage info.I don’t recommend trying to decifer the Aurena metadata documents, but if you need metadata that isn’t exposed from an existing projection I would engage with @Nils Wendelöv
I don’t have an onscreen solution for you, however the AllProjections service endpoint has some of the information referenced above. Unlike the name, there are a couple restrictions on the list returned (Virtuals are excluded) however it does contain some of the mapping metadata.Here’s a sample link to an internal environment: https://ifscloudr2bnt-lkp.rnd.ifsdevworld.com/main/ifsapplications/projection/v1/AllProjections.svc/ProjectionsYou can also use the details from AllProjections to craft oData complient requests directly to the ODP server. We use this internally to populate some of the menus in the Workflow Designer.
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.
