Skip to main content
V
vladislavm9556
August 29, 2022
Solved

Using same process model for different interfaces

  • August 29, 2022
  • 4 replies
  • 0 views

Hi!

Is there any possibility to use the same model for different interfaces?

In my case: I have an interface where I insert an ID and delete the data with that ID, I used this interface as a start form for my process model.

Now I created an interface with a possibility to select multiple rows in a grid and I want to be able to delete all of them by pressing a button. My question is: is there any possibility to use the same process model or I have to create another one?

Thank you!

Best answer by deepakg681722

Instead of start form, you can pass the required parameter to process model by calling that process model from a standalone interface by using startProcess function.

4 replies

D
deepakg681722
August 29, 2022

You can use the same process model by making process variable as of array type. You can create constant for the process model and use it to call at multiple places.

V
vladislavm9556Author
August 29, 2022

I'm not sure how a constant would solve my problem. I have 2 interfaces and I use them as the start form for my process models - if I would have only one process model, I wouldn't be able to choose 2 different start forms. And currently my site pages are linked to process models, so I would remain with only one interface...

D
deepakg681722Answer
August 29, 2022

Instead of start form, you can pass the required parameter to process model by calling that process model from a standalone interface by using startProcess function.

    peter.lewis
    peter.lewis
    Employee
    August 29, 2022

    If you want to reuse the process model, I would actually suggest a different approach from the previous poster - this is a great use case for a sub-process. You can create multiple process models that each refer to their own interfaces, then have the next step in the process model refer to this shared process model as a sub-process. Then you get the best of both worlds: the reusability of having the same logic in both processes, and the flexibility of using different interfaces.

      Terms & ConditionsAccessibility statement