Ensuring Internal Process Variables Remain Hidden in API Request in Kogito BPMN
pawan saha
Hello Team,
I’m new to Kogito, so I appreciate your patience if my question seems basic.
I have an API that accepts a Workflow object as input. However, the Bpmn object is also appearing in the request, which I do not intend to expose.
I have defined two process variables: (Refer the below Image 1)
- workflow: Should be included in the input request.
- bpmn: Should be used internally within the process, remain hidden from the request, and be accessible in subsequent tasks for updates.
To prevent bpmn from being exposed, I removed it from Data Inputs and Assignments (Refer the below Image 2). However, it is still appearing in the input request (Refer the below Image 3). How can I ensure that bpmn remains internal, is available for updates in subsequent tasks, and does not appear in the API request?
FYI – I tried defining bpmn as a global variable and also tagged it as "internal", "output", and "tracked", but none of these approaches worked.
Image1:
Image 2:
Regards,
Pawan
pawan saha
Pere Fernandez
Hi Pawan, I think that tagging the variable as internal should do the work.
If you look at the compact architecture example, we are doing that to keep hr_approval/it_approval varoables not visible in the hiring process schema.
--
You received this message because you are subscribed to the Google Groups "Kogito development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kogito-developm...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/kogito-development/CAMVXLxqwvncH_q9G_Xuz%3DrnKnhOC%2BPdJXh3uewhqQ_zf1WPpOg%40mail.gmail.com.
pawan saha
I am trying to model Workflow.java as the input and generate Bpmn.java as the output.
I have defined two process variables and tagged Workflow.java as the input and Bpmn.java as the output.
For a user task, I have set "workflow" as the input and "bpmn" as the output.
pawan saha
Hello Team,
I am working with Kogito and exploring options to set a dynamic name for an XOR gateway. In my process, I have a Service Task named "Flow Decision", which provides an output based on which the workflow proceeds along different paths. Following this Service Task, there is an XOR gateway (highlighted with a red circle in the attached diagram).
I would like to know if it is possible to assign a dynamic name to this XOR gateway based on the decision made in the service task. If so, could someone guide me on how to achieve this? Specifically, I am looking for a way to reflect the dynamic name at runtime for clarity and better process visualization.
