BPM, Workflow, and Case

Hello Community Members,

                     Hope everyone is doing great.

We have Client Side Human Service(CSHS), where we have a service integrations in the CSHS calling  service flows.

So, in my first service flow attached to the CSHS - there is XMLElement initialization ,and  in the same service flow XMLElement is parsed and mapped to variable of Map type.

Now , when I debug the value for Map type variable the value persists in the service flow, but the moment token moves to the next activity from the service flow in the CSHS , the Map value at the CSHS is empty/undefined.(there is no re-initialization is done).

And, also when I try to pass the XMLElement object from the current service flow(i.e where initialization was done) to next service flow in the CSHS, its passed as undefined.

XMLElement from service flow to CSHS , the value is passed correctly , the vice versa its undefined. 

Is this the expected behavior or its a bug, because the same implementation when designed in Process and Service flows its working fine and as expected. 

Any solution or reference to the above issues would be really of great help.

Thank You.

------------------------------
Gona Deepak
------------------------------

Gona,

Can you please click on the flow line going out of the Coach, go to the Implementation tab settings and make sure that 'Save execution context of layered task implementation' option (or the like) is checked? Let us know if that was the problem or not.



------------------------------
Ajay Katre
Sacramento CA
------------------------------

Original Message:
Sent: Wed October 21, 2020 03:51 AM
From: Gona Deepak
Subject: Map type BO value persistence in Client Side Human Service from service flow

Hello Community Members,

                     Hope everyone is doing great.

We have Client Side Human Service(CSHS), where we have a service integrations in the CSHS calling  service flows.

So, in my first service flow attached to the CSHS - there is XMLElement initialization ,and  in the same service flow XMLElement is parsed and mapped to variable of Map type.

Now , when I debug the value for Map type variable the value persists in the service flow, but the moment token moves to the next activity from the service flow in the CSHS , the Map value at the CSHS is empty/undefined.(there is no re-initialization is done).

And, also when I try to pass the XMLElement object from the current service flow(i.e where initialization was done) to next service flow in the CSHS, its passed as undefined.

XMLElement from service flow to CSHS , the value is passed correctly , the vice versa its undefined. 

Is this the expected behavior or its a bug, because the same implementation when designed in Process and Service flows its working fine and as expected. 

Any solution or reference to the above issues would be really of great help.

Thank You.

------------------------------
Gona Deepak
------------------------------

Dear Ajay,
           Thanks for the inputs - we had tried that option earlier by checking those configurations it did not help.

We also tried all the combinations by checking one and not checking the other and not checking both - there was no change in the result or values.

Thank You

------------------------------
Gona Deepak
------------------------------

Original Message:
Sent: Wed October 21, 2020 09:42 AM
From: Ajay Katre
Subject: Map type BO value persistence in Client Side Human Service from service flow

Gona,

Can you please click on the flow line going out of the Coach, go to the Implementation tab settings and make sure that 'Save execution context of layered task implementation' option (or the like) is checked? Let us know if that was the problem or not.

------------------------------
Ajay Katre
Sacramento CA

Original Message:
Sent: Wed October 21, 2020 03:51 AM
From: Gona Deepak
Subject: Map type BO value persistence in Client Side Human Service from service flow

Hello Community Members,

                     Hope everyone is doing great.

We have Client Side Human Service(CSHS), where we have a service integrations in the CSHS calling  service flows.

So, in my first service flow attached to the CSHS - there is XMLElement initialization ,and  in the same service flow XMLElement is parsed and mapped to variable of Map type.

Now , when I debug the value for Map type variable the value persists in the service flow, but the moment token moves to the next activity from the service flow in the CSHS , the Map value at the CSHS is empty/undefined.(there is no re-initialization is done).

And, also when I try to pass the XMLElement object from the current service flow(i.e where initialization was done) to next service flow in the CSHS, its passed as undefined.

XMLElement from service flow to CSHS , the value is passed correctly , the vice versa its undefined. 

Is this the expected behavior or its a bug, because the same implementation when designed in Process and Service flows its working fine and as expected. 

Any solution or reference to the above issues would be really of great help.

Thank You.

------------------------------
Gona Deepak
------------------------------

The simple answer is - you cannot use those datatypes in CSHS because those are not JavaScript datatypes. 

But I am wondering why do you need to pass those datatypes in CSHS ?
Can you please explain the use case, then probably we can think of alternatives ?




------------------------------
Atanu Roy
------------------------------

Original Message:
Sent: Wed October 21, 2020 03:51 AM
From: Gona Deepak
Subject: Map type BO value persistence in Client Side Human Service from service flow

Hello Community Members,

                     Hope everyone is doing great.

We have Client Side Human Service(CSHS), where we have a service integrations in the CSHS calling  service flows.

So, in my first service flow attached to the CSHS - there is XMLElement initialization ,and  in the same service flow XMLElement is parsed and mapped to variable of Map type.

Now , when I debug the value for Map type variable the value persists in the service flow, but the moment token moves to the next activity from the service flow in the CSHS , the Map value at the CSHS is empty/undefined.(there is no re-initialization is done).

And, also when I try to pass the XMLElement object from the current service flow(i.e where initialization was done) to next service flow in the CSHS, its passed as undefined.

XMLElement from service flow to CSHS , the value is passed correctly , the vice versa its undefined. 

Is this the expected behavior or its a bug, because the same implementation when designed in Process and Service flows its working fine and as expected. 

Any solution or reference to the above issues would be really of great help.

Thank You.

------------------------------
Gona Deepak
------------------------------

Thanks Atanu.

That gives a logical ending to our question. 

As there was no restriction on the object mapping to the map datatype in the CSHS and we tried to use the Map and XMLElement to pass the objects across the service.
 
As an alternative we  can achieve our requirement by designing as process or service flow.

------------------------------
Gona Deepak
------------------------------

Original Message:
Sent: Wed October 21, 2020 11:13 AM
From: Atanu Roy
Subject: Map type BO value persistence in Client Side Human Service from service flow

The simple answer is - you cannot use those datatypes in CSHS because those are not JavaScript datatypes. 

But I am wondering why do you need to pass those datatypes in CSHS ?
Can you please explain the use case, then probably we can think of alternatives ?




------------------------------
Atanu Roy

Original Message:
Sent: Wed October 21, 2020 03:51 AM
From: Gona Deepak
Subject: Map type BO value persistence in Client Side Human Service from service flow

Hello Community Members,

                     Hope everyone is doing great.

We have Client Side Human Service(CSHS), where we have a service integrations in the CSHS calling  service flows.

So, in my first service flow attached to the CSHS - there is XMLElement initialization ,and  in the same service flow XMLElement is parsed and mapped to variable of Map type.

Now , when I debug the value for Map type variable the value persists in the service flow, but the moment token moves to the next activity from the service flow in the CSHS , the Map value at the CSHS is empty/undefined.(there is no re-initialization is done).

And, also when I try to pass the XMLElement object from the current service flow(i.e where initialization was done) to next service flow in the CSHS, its passed as undefined.

XMLElement from service flow to CSHS , the value is passed correctly , the vice versa its undefined. 

Is this the expected behavior or its a bug, because the same implementation when designed in Process and Service flows its working fine and as expected. 

Any solution or reference to the above issues would be really of great help.

Thank You.

------------------------------
Gona Deepak
------------------------------

If you are trying to pass complex object, you can create JSON string and pass it across and parse that to business object again in service flow.


------------------------------
Atanu Roy
------------------------------

Original Message:
Sent: Wed October 21, 2020 11:39 AM
From: Gona Deepak
Subject: Map type BO value persistence in Client Side Human Service from service flow

Thanks Atanu.

That gives a logical ending to our question. 

As there was no restriction on the object mapping to the map datatype in the CSHS and we tried to use the Map and XMLElement to pass the objects across the service.
 
As an alternative we  can achieve our requirement by designing as process or service flow.

------------------------------
Gona Deepak

Original Message:
Sent: Wed October 21, 2020 11:13 AM
From: Atanu Roy
Subject: Map type BO value persistence in Client Side Human Service from service flow

The simple answer is - you cannot use those datatypes in CSHS because those are not JavaScript datatypes. 

But I am wondering why do you need to pass those datatypes in CSHS ?
Can you please explain the use case, then probably we can think of alternatives ?




------------------------------
Atanu Roy

Original Message:
Sent: Wed October 21, 2020 03:51 AM
From: Gona Deepak
Subject: Map type BO value persistence in Client Side Human Service from service flow

Hello Community Members,

                     Hope everyone is doing great.

We have Client Side Human Service(CSHS), where we have a service integrations in the CSHS calling  service flows.

So, in my first service flow attached to the CSHS - there is XMLElement initialization ,and  in the same service flow XMLElement is parsed and mapped to variable of Map type.

Now , when I debug the value for Map type variable the value persists in the service flow, but the moment token moves to the next activity from the service flow in the CSHS , the Map value at the CSHS is empty/undefined.(there is no re-initialization is done).

And, also when I try to pass the XMLElement object from the current service flow(i.e where initialization was done) to next service flow in the CSHS, its passed as undefined.

XMLElement from service flow to CSHS , the value is passed correctly , the vice versa its undefined. 

Is this the expected behavior or its a bug, because the same implementation when designed in Process and Service flows its working fine and as expected. 

Any solution or reference to the above issues would be really of great help.

Thank You.

------------------------------
Gona Deepak
------------------------------