Skip to main content

Hello community,

I have created a workflow from scratch for importing currency rates from different sources based on the company. This is the workflow

Workflow details

 

I added projection actions to my workflow

 

 

When i validate the workflow it works. When I manually use update currency rates button with start now, the rates are created. But scheduled DB task is not creating currency rates although the background job is triggered successfully.

Any idea?

Thanks

Furkan

Hi, 

How is the scheduled DB task is created ? can you shae bit more information into that setup. how is the Workflow set to trigger from the db task ?

Hello ​@kamnlk 

I am using IFS provided database tasks which is created from currency rate type or centralized currency rate handling window.

 

 

Here are the tasks.

 

 

Hello ​@kamnlk 

Did you have time to check whether can you schedule it?

Thanks

Hi,

From the looks of the configuration, I noticed the workflow name is not the standard naming used for the currency rate update workflow. This could be the reason why It would trigger for projection action/button click and may not be triggering when in schedule mode, as it may be expecting a standard workflow to be available. 

 

ref: Currency Rate Update (ACCRUL) - Technical Documentation For IFS Cloud

Hello ​@kamnlk 

Thank you for your reply. I see the case now. If I would download the workflow, can i upload to the finCurrencyTypeUpdate workflow? Or do i need to build one more time?

Thanks

 

Hi ​@Furkan Zengin ,

You could download and rename the workflow,

in the downloaded bpmn diagram, first open it in a text editor then in the diagram xml rename all references of your current workflow name to finCurrencyTypeUpdate. Then upload it to the system. 

Hello ​@kamnlk 

Thank you for your guidance. I could import it as a new version to existing finCurrencyTypeUpdate. One last question with existing TrCurrencyRateUpdate workflow. When i try to undeploy active version, i get BPA_NOT_SINGLE_RESULT error. Do you know what could be reason?

Thanks

Furkan

 

 

Hi,

This error usually comes where there is a duplicate workflow entry. what are the steps you taken to get to this error? 

in the meantime you can try following ways and see if it helps,

  1. disabling/deleting the projection actions from this workflow, then try to undeploy
  1. try to deploy version 1 again so it auto undeploy the version 2, then Undeploying the version 1 again

Hi ​@kamnlk 

After deleting projection actions, I was allowed to undeploy the workflow version. Thank you very much for your incredible support.

Have a great day

Furkan

Reply


Terms & ConditionsCookie settings