So overall I must say that I believe the new Decisions sub-service is better than the previous Business Rules service (as part of Workflow Management). Īt the moment the Version is required in the API call but in future releases I believe this is being removed. In Decisions, you use the 3 dots icon in the top right hand corner of the Decisions UI and then click. In Business Rules you had to include the ID field using the Settings cog to be able to retrieve the Rule service ID. Retrieving the ID’s that need to be used in the API call are a bit difficult to find.You can see here the tabs view making it faster and easier to navigate to different artifacts without multiple browser sessions.įigure:9 Decisions artifacts tabular view Seeing the information around Decision deployment is really good – who created and who modified and the date it was modified are nice additions.įigure:8 Decisions artifacts – you can see Data types and Decisions on one page.The import and output options are pretty much the same as they were and similar formats for the files.You can see that this parameter has the List checkbox active meaning multiple records will be returned.įigure:6 Output parameter List option (to set to ALL MATCH) In recent updates I also believe users now have the choice to set this, whereas before it was set automatically. With the new tooling you simply select the checkbox and this automatically sets the decision to ALL MATCH. Previously in Business Rules you defined a Table and when this was the result set it meant retrieval of ALL MATCHING records. As far as the new tooling is concerned there is a major difference when you want to retrieve a table of records.I also want to call out other functionalities I feel are implemented better in Decisions than Business rules. Cannot see running history (and dates) of deployments – can only view 1 at a time.No tile available atm to integrate into Launchpads.New tooling and takes a bit getting used to.Easy to use API’s – these are different API’s!.Better User experience (less steps) especially with the Visual UI representation.Simple deployment method (Save, Release, Deploy).Can maintain notes against each release.Can release and deploy different versions.Less artifacts involved and multiple activations NOT required.Decisions can be set up faster than Business Rules – less artifacts!.Anyway, let me go through my analysis and compare Business Rules vs Decisions. Forcing customers into the whole SAP BPA suite I don’t agree with and it may actually stop customers from enabling it. That is, they do not have to buy SAP Build Process Automation if they only want to use Decisions. So, overall I am happy that Decisions now cover most of what was there previously but I still stand by my view of it being a completely separate service, with it’s own licensing arrangements to offer customers better flexibility. What I can say is that we are actively using the Decisions functionality (as part of SAP BPA) in our current projects and it not only offers all of the functionality Business rules used to offer but it is also faster.
At the time it was difficult to work through the tooling as it was very different to the previous service. A few months ago I wrote a blog post about SAP Build Process Automation and the failure for handling the Business Rules service – from a SAP BTP perspective.
0 kommentar(er)
