Question

2
Replies
220
Views
JBENCHERIF Member since 2011 2 posts
Ordina
Posted: October 4, 2016
Last activity: October 10, 2016
Closed

Available properties (within NBA strategy)

In our NBA project we have a requirement where the strategy designers have to fill certain properties, which will be used to do a soap connect later in the process. These properties are defined as name/value pairs in the soap interface. The requirement stated that the designers need to be able to start using new properties without the need of a new deploy, nor a change in the soap request/response interface.

We already created a working process where the strategy designers can fill the name/value pairs with the values they want, and they are added in the final soap request. Working as intended...

The downside of this approach, is that different strategy designers can come up with different names for the same properties. For example strategy designer A creates the name/value pair : MaximumAge / 18, where strat designer B came up with : MaxAge / 18. Ofcourse this can be solved by making good procedures and documentation about the used names... but...

What I would really like is to limit the options for the strategy designer.

Im trying to come up with a way to...

* Have 1 place where the strategy designers can create and maintain the values that can be used for 'name' in the name value pairs (name/age/birthplace/etc.).

* Somehow use that data as only possible valid values for the name property in the name/value pair.

Is there a clever way to archieve this without customizing/specializing out of the box functionality? Ideally all needed rules to maintain this should be available to the strategy designer (therefor in the overlay). How would you approach this?

Many thanks in advance,

Jamäl

***Updated by moderator: Lochan to add Category***

Data Integration
Moderation Team has archived post
Share this page LinkedIn