Change the Workflow creator ID

[Former Member]

Hi All,

All the workflows are initiated with WF-BATCH in one particular client and this ID configured with US time.

But now client want the to use a new ID WF-A-BATCH(which is configured to ASIA time) for particular set of operations only.Since there is a restriction on the RFC definition(one definition per Client).

Is there any way to change the workflow ID after it triggered with WF-BATCH. So that the operations can be done with WF-A-BATCH.

Thanks in advance.

With Regards,

Aditya

[Former Member]

We are passing the document date to the BAPIS used before creating the documents at each step. Now the date issue is resolved.

Thanks to all.

Regards,

Aditya

[former_member185167]

Hello,

Could you explain why you think a WF-A-BATCH user is necessary, perhaps it's not the case.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Hi Rick,

Currently, we are facing the Date issue in the 2nd leg documents.

Details of the issue:-

***1st leg documents are manually created and 2nd leg documents are automation(workflows) using the 1st leg document.

Issue: - If the user in Asia creates the 1st leg (all the documents are in Asia time) and the workflow is triggered to create the 2nd leg documents. Since the workflow creator is WF-BATCH(US time), all the 2nd leg documents are in US time.

We cant change the WF-BATCH user setting, since it is used across.

Please suggest any solution for the same.

Thank you in advance

Regards,

Aditya

[former_member185167]

Hello,

To avoid problems with timezones, workflow often chooses to store dates as timezone GMT/UTC.

Perhaps that is possible in your case as well.

A date and time in itself is meaningless if you don't give a time zone so maybe you should store the time zone as well, or store the attribute you're worried about (document creation date?) as a separate attribute.

regards

Rick Bakker

Hanabi Technology

[Former Member]

Aditya,

I dont think so. The current workflow instances will not refer back to new id and this user is one per client. That is all workflows in one client has to use a single WF-Batch user.

If you are switching the user to other timezones , then I think the new instances will pickup your new batch user.

- Amit Jain