Moment of xECM business workspace creation

AppWorks Tips · December 11

Hi,

We create case instances in runtime, which also triggers the creation of BWs in OTCS (xECM). But from an AppWorks perspective, what is the moment of BW creation when we also have onInit and onCreate rules fired running heavy BPMs? Is it after those rules, before, or is it a parallel thingy?

Best regards,
//Antal

AppWorks Tips · December 17

@Sander_Beutick_OT_PS and @Saurabh Kumar

Great answers; after some R&D this is the conclusion from our project perspective:

onInit rules triggering BPMs are outside scope as nothing has been created/saved yet in the DB! ✅

onCreate we see our BPMs being triggered and parallel the creation of a BWs passes by. Because creating a BW takes some time, we must create a delay (only possible on a long-lived BPM!) to wait before we continue the onCreate BPM.

If an onCreate BPM should be short-lived, we need to do a different implementation. In that case, we probably need an onPropChange rule (when BWs-ID is set on the entity) to start a BPM doing our BWs-related actions.

Maybe an extra clarification comment/recommendation from PS on this choice could be interesting?

//Antal

Saurabh Kumar · December 11

The Business Workspaces are created when the entity (with Business Workspace building block) is saved in AppWorks.

Once Business Workspace creation is successful/failure then the entity is saved with proper status.

Sander_Beutick_OT_PS · December 11

it is tempting to look in the content server logs to see when the creation moment is registered.

i am curious if those heavy BPMs fall into the 'transaction' of the creation of the case and the BWS, ergo can you enforce an atomic manner of handling success / failure that results in a full rollback upon exception or a creation upon succes?

thus can the ECMLinkService integration (tomcat) wait until prerequisites are handled? that is your question i guess?

i will ask my colleagues ( you know them very well i think.) and when i know, you will also :)

ok so i asked my valued colleague and he responded:

'.a BWS is generated after the Case Create. During an OnInit there is no BWS created or present.
regarding the BPMs : make sure that they are short-lived.', but i guess that this is no news to you.

AppWorks Tips · December 17

@Sander_Beutick_OT_PS and @Saurabh Kumar

Great answers; after some R&D this is the conclusion from our project perspective:

onInit rules triggering BPMs are outside scope as nothing has been created/saved yet in the DB! ✅

onCreate we see our BPMs being triggered and parallel the creation of a BWs passes by. Because creating a BW takes some time, we must create a delay (only possible on a long-lived BPM!) to wait before we continue the onCreate BPM.

If an onCreate BPM should be short-lived, we need to do a different implementation. In that case, we probably need an onPropChange rule (when BWs-ID is set on the entity) to start a BPM doing our BWs-related actions.

Maybe an extra clarification comment/recommendation from PS on this choice could be interesting?

//Antal

Sander_Beutick_OT_PS · December 18

Hi @AppWorks Tips (Antal),

With one of my previous customers, their case management system is designed in an a-synchronous manner. The Case is created, the BWS is staged and then a scheduled webreport does all the configuration on / with the BWS before moving it to its 'final' location.

They found that the whole transaction containing all steps of what a full deployed BWS should represent was not ready yet (so without the staging step). Still Appworks presented the BWS to the end user as if ready and fully configured ( roles, permissions, security clearance settings etc.)

So yes, the BWS creation is the slowest in the chain it seems and people get creative working around its quirks.

Moment of xECM business workspace creation

Best Answer

Answers

Categories