Hi Bryan, You should be able to do this using a workflow. In the workflow configurations, projection action you can listen to SupplierForPurchasePartHandling → PurchasePartSupplier_Default() with process enrichment type with After timing. In the workflow you can set the value for the “Discount” to null to get this behavior. Hi @kamnlk if the timing is set to after, wouldnt this error out no matter what since the mandatory field would be set to null? Are you aware of any IFS functionality that allows for the modification of data on retrieval of fields? I noticed that for customer order lines, when you enter a qty the prices update automatically even though the line hasnt been saved yet. Thanks, Bryan Hi @bdoucette , Not quite, in this case we are not modifying/intercepting the api call that creates the purchase part. we are only changing the api response that populates the default values in the UI (PurchasePartSupplier_Default). Using this approach, we are preventing
@kamnlk are you allowed to update from 0 to null if the field is set as mandatory? What about creating a User interaction WF and once the SFPP is saved, trigger the WF and ask the user for the Discount% → read user’s response and update SFPP? Sorry i missed to reply about the latter part; Yes, using a User interaction WF is another approach for this use case.
yes in this case we are overriding the value of the default() function. we are not changing any value from database, just the client-side prefilled values.the expected output would be like this the projection action configuration used
Hi Bryan,You should be able to do this using a workflow. In the workflow configurations, projection action you can listen to SupplierForPurchasePartHandling → PurchasePartSupplier_Default() with process enrichment type with After timing. In the workflow you can set the value for the “Discount” to null to get this behavior.
I don't think row key is supported from the DocumentRevisionHandling API. that could be the casewould it be possible to enable doc_no in the event attributes? from the screenshots it seems only rowkey and CF$_SP_INCL_IN_SFORCE_RPT is enabled as attributes.
Hi,I don't think the new line character will work with user forms. Splitting the lines using multiple records of the same local will only use the value declared last as the value for that local.How ever there is a potential workaround that we can use to show these long texts using a “text” field type in user forms.
Hi, In the exception it says the “DocNo” value is not coming in as an input to workflow. you may need to enable that attribute on the event to make it available to workflow. You can also check which attributes gets passed into a workflow by using “Start Watch” option on the workflow when executing and checking the observations.
Hi,Update the data on the "Customer order" screen, as in changing values on customer order by utilizing the change you just did can be done using BPA by configuring a projection action to the api call.but Refreshing a client page using a BPA is not a supported scenario.
From workflow side there is no workaround as this is the indented behavior.As a workaround you can check if there is another API(s) available that will cover the use case but does not contain rollbacks
Hi, The error you are getting due to a known limitation in workflow where we cannot use APIs that contain rollbacks inside the workflow.refer: Known Limitations - Technical Documentation For IFS Cloud According to the Workflow transaction management policy, it is not allowed to call API's which having the implicit commit, rollback, savepoint or Pragma Autonomous blocks, through a Workflow.
In workflow side when you omit the ResourceSeq value it will not allocate a value to ResourceSeq. (this could make this value null). this behavior should be similar to that in postman. if you define the value as NULL that could cause this error you can also check if the ResourceSeq attribute gets passed into the workflow as an input.. if that's the case you can try to remove that value inside the workflow before calling the create resourcegroup task.
How are you executing the workflow?When we run a workflow in inspection/debug mode, execution will not change data in the system. It will only do a test run to see if the workflow can be executed without a problem.
Hi,It seems you also need to pass in WoNo attribute when creating a new Work Task. Can you give it a try, and see? Work Task CreationWorks in debug
Already have an account? Login
No account yet? Create an account
Enter your 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.
