Skip to main content

How to Fix :Error: The execution context was not saved due to the following error: CWTBG0019E

Why do you get this error ?

This error comes when you are assigning some value to a tw.local variable in CSHS(Client Side Human Service) ,but that variable in not yet created or type is mismatch with the value being assigned.

Solution:-
Whenever you get this error, then follow these steps:

Step 1:In CSHS recognise the line flow in which this error is coming.

Step 2:Starting from first line ,implement : Check both options.
Step 3: Run the flow ,if error comes again then buggy code is in Javascript written just before the line.Otherwise continue the same to next line.

Step 4:Remove Save execution context after bug fixing as per your requirements.

Comments

Post a Comment

Popular posts from this blog

How to Fix: CWTBG0586E: Cannot start BPD because the snapshot or BPD is in the wrong state. Status : 409

Reason: This issue comes when you are trying to start a process using rest API but that snapshot is not activated. Mostly this issue comes in development environment. Solution(When Process Designer is available):- Step 1 :- Go to process designer. Step 2 :- Click on your process App name. Step 3 :- Click on the down "Arrow" symbol which is placed just right side of the snapshot name. Step 4:- Select "Activate" option. Solution (When Process Designer is not available):- Step 1:- Open process Admin with proper authorization. Step 2:- Select the installed process app. Step 3:- Activate the process App.
1 comment
Read more

Move token using Rest API in IBM BPM

Why do you need this ? There can be multiple reasons to move token, like:- Suppose you are on a step and after some action "Save execution context" is implemented in between, then you need to move the token and point to the same step. Step 1: Open Rest API Select " Business Process Manager REST APIs" ,then select " Process API ", then select "Current State". Step 2: Enter Process Instance Id (In this case-670) & then Click on Execute Call. Step 3 :Look for Token Id (In this case Token Id-5) Step 4 : Look for Source Step Id (In this case - a0649e22-26fc-4529-8055-9775b6eae14c) Step 5 : In Process API list Click on " Move Token ". Step 6: Fill Process Instance ID,Token ID & Target Step Id , Then  click on execute call . Step 7 :Status 200 shows that Token moved successfully.
Post a Comment
Read more