Technology Blogs by SAP
Learn how to extend and personalize SAP applications. Follow the SAP technology blog for insights into SAP BTP, ABAP, SAP Analytics Cloud, SAP HANA, and more.
cancel
Showing results for 
Search instead for 
Did you mean: 
kumarraj_moorthy
Explorer
SAP Cloud Applications Studio: What’s New in 1611

Here is a preview of what’s coming up with 1611 release of SAP Cloud Applications Studio.

AfterLoading Event for XBOs: SAP Cloud Applications Studio 1611 supports creation of AfterLoading event for extension BOs (XBOS). Till 1608, the AfterLoading event was supported only for Custom BOs. The AfterLoading script is executed during the loading of the UI screen when the system reads a node instance of a business object.

Note that the following cannot be done in the AfterLoading event

  1. Modify a persistent field

  2. Create or delete a node

  3. Call an action



Tasks:

  • In the Solution Explorer, right click the XBO and select Create Script Files

  • In the Create Script Files dialog box, select the Event:AfterLoading. The Event-AfterLoading.absl file is generated.

  • Implement the business logic in the generated .absl script file.

  • At runtime, when the UI screen corresponding to the XBO is loaded, the AfterLoading script logic shall be executed.


Note: This feature is not supported for all the standard extension BOs. Refer Studio help documentation for list of supported BOs.

 

API to read Business Role:

A new function GetAssignedBusinessRoles is added to the ‘Context’ reuse library.

This function retrieves all the assigned business roles for the logged-in business user and returns a collection. The collection supports GetFirst(), GetLast() and Count() functions.

GetFirst() – Gets the First assigned business role from the collection.

GetLast() – Gets the Last assigned business role from the collection.

Count() – Gives the count of the assigned business roles.

Here is a code snippet on how to use the api.




New AccessContext:

A new AccessContext ‘SalesOrganization(9001)’ is introduced in 1611.

Till 1608, only the accesscontext ‘Employee’ and ‘EmployeeOrTerritory’ was supported.

Now with the new ‘SalesOrganization(9001)’ accesscontext, the access to the instances can be restricted based on the sales organization of the employee in the organizational hierarchy.

Code snippet to use in the ABSL.

 



Also refer the following blogs on this topic

http://scn.sap.com/community/business-bydesign/studio/blog/2015/12/01/implementing-access-control-on...

 

Configuration setting in UI Designer:



 

Note: This new accesscontext is available only for C4C.

For more details on access control and how to use refer the following blogs

Implementing Access Control on Custom Business Objects

Access Control Management: Basics of access control and business roles

 

New Enhancement option:

A new Enhancement option, BADI Implementation is introduced to restrict the display of certain fields like mobile, email etc in the Enterprise search results based on the category.

Here are the details:

Enhancement option: ‘EnterpriseSearchRestrictResultDisplay‘

Namespace: http://sap.com/xi/AP/CRM/Global

Below are some screenshots on how to create the Enhancement Implementation.




This Enhancement option can be used to implement rules to hide the result data display. Below is the code snippet.
7 Comments