best way for parameter handling when mixing shared and application components?

[Michael Gebhardt]

Hello fellow designers,

 

we hit a wall today, when we tried to set up our first application where we need to enhance the stuff we provide with a shared component.

 

What we currently did is the following:

• Assign the shared component to the application
• Create a “local” component.
• Both are assigned to the same server type
• This way we can use both components in the design of the process

 

BUT, now we’re having the following problem:

In the shared component we’re setting a parameter ParA, this ParA we need in the local component as well. How can we solve this?

 

Our only solution we came up with at the moment would be, that we need to enhance the shared component with an ROC update string parameter action, that sets the local ParA version. The problem with this one is, that we would need this action for all parameters we might need and we also would need to have naming conventions for the local components, as it is a string in the ROC action.

 

Any help/ideas would be appreciated.

 

Thanks.

 

best regards

michael

 

p.s. keep in mind, that we're not allowed to use application parameters in shared components

[Jacky_Mahadab]

Hi

Did you tried create parameter in local component (e.g param-b) and in the process level set the value for param-b to be ParA from the shared component?

[Michael Gebhardt]

Hi Jacky,

 

awesome, this seems to work!

 

thanks.

 

best regards

michael