{"id":42606,"date":"2024-07-30T12:41:27","date_gmt":"2024-07-30T10:41:27","guid":{"rendered":"https:\/\/xiting.com\/?p=42606"},"modified":"2026-02-24T19:42:26","modified_gmt":"2026-02-24T18:42:26","slug":"xiting-central-workflows-new-functions-with-service-pack-5","status":"publish","type":"post","link":"https:\/\/xiting.com\/en\/news\/xiting-central-workflows-new-functions-with-service-pack-5\/","title":{"rendered":"Xiting Central Workflows: New Functions with Service Pack 5"},"content":{"rendered":"\n

As the saying goes, \u201cGood things come to those who wait\u201d. This also applies to the new release of Service Pack 5 (SP5) of our product Xiting Central Workflows (XCW)<\/a>. After more than a year of defining requirements, development and testing, we are not only presenting brand new functions, but also completely rethought use cases (XCW and SAP Cloud). But let’s go back to the beginning: with XCW, we offer you standardized workflows according to SAP best practice for the most important application scenarios in user administration of primarily SAP systems in our experience. In SP5, you can also use the tried-and-tested workflows for creating\/changing users, assigning and revoking authorizations and the combination as usual – only even better and easier. The Fiori interfaces and password self-service are also still available and include some much-awaited features.<\/p>\n\n\n\n

We present some of the new functions and use cases of the new release below.<\/p>\n\n\n\n

Business Roles<\/h2>\n\n\n\n

We want to improve the user experience and simplify the application for authorizations by using business roles. These are containers with cross-system authorizations that are maintained in XCW customizing. In future, the end user will only apply for business roles that can be found using simple search options. This significantly reduces the number of selection options.<\/p>\n\n\n\n

The application process remains unchanged. The business roles can be searched for and requested either in the user creation request or in the role request. The business role owner must then approve the assignment and, if a risk is identified by XAMS CRAF<\/a>, it must be released or mitigated by the risk owner.<\/p>\n\n\n\n

Figure 1 shows the business role wizard:<\/p>\n\n\n\n

\"\"
Figure 1: Business Roles Wizard<\/figcaption><\/figure>\n\n\n\n

Figure 2 shows the view of the requested business role:<\/p>\n\n\n\n

\"\"
Figure 2: Requested Business Role<\/figcaption><\/figure>\n\n\n\n

Extension of the LDAP integration<\/h2>\n\n\n\n

The previous LDAP integration included an LDAP search that transferred information from identities from sources such as the Active Directory to user applications in the XCW and matched them accordingly. These applications could be processed and submitted manually.<\/p>\n\n\n\n

With SP5, it is possible to set up jobs that regularly read in data via LDAP and determine whether new identities have been created or existing identities have been changed. This generates automatic user requests that must be approved by the user managers in the XCW.<\/p>\n\n\n\n

In addition, the popular LDAP search is now also available in the user creation and role assignment requests (business roles and PFCG roles):<\/p>\n\n\n\n

\"\"
Figure 3: Search via LDAP in Fiori<\/figcaption><\/figure>\n\n\n\n

Dynamic Risk Managers<\/h2>\n\n\n\n

With SP5, it is possible to store the risk owners for each risk individually in XAMS CRAF. As soon as a risk is created by an assignment, XCW receives the corresponding risk owner from CRAF and this person takes over the approval step in XCW. The central maintenance of a group of risk owners is still available. A customizing switch can also be activated, making it possible to enter the risk owner individually when submitting the application.<\/p>\n\n\n\n

Find out more about XAMS CRAF in this new webinar:<\/p>\n\n\n\n

\n
On-Demand Webinar XAMS<\/a><\/div>\n<\/div>\n\n\n\n

In addition, the approval of risk owners in Fiori has been optimized and mitigation is now also possible:<\/p>\n\n\n\n

\"\"
Figure 4: Mitigation in Fiori<\/figcaption><\/figure>\n\n\n\n

Manager Approval<\/h2>\n\n\n\n

Previously, there was the approval step of the role owner and occasionally the risk owner. SP5 introduces an additional approval step – that of the manager. This has been repeatedly requested by our customers in the past and now we can meet this requirement. In the first version, a simple mapping table will be implemented in which users must be assigned to their managers. If XAMS CRAF is used, the approver can also see whether there are any conflicts.<\/p>\n\n\n\n

Figure 5 shows the manager approval in the SAP GUI interface and Figure 6 in the Fiori interface.<\/p>\n\n\n\n

\"\"
Figure 5: User Manager Approval SAP GUI<\/figcaption><\/figure>\n\n\n\n
\"\"
Figure 6: User Manager Approval Fiori<\/figcaption><\/figure>\n\n\n\n

Further Optimizations<\/h2>\n\n\n\n

Many other optimizations have been successfully implemented, particularly as a result of feedback from our customers who are already using XCW:<\/p>\n\n\n\n