GAC Guidelines

Implications & Guidelines

By default, GAC remains disabled. Therefore, even after upgrading to Connect 2.9.3 product will continue to use the existing permission model. However, for new and existing customers, enabling GAC can bring some changes.

New Customers

Those who do a fresh install of Adeptia Connect 2.9.3, can enable GAC and start working with the new permission model after enabling GAC. You can refer to the documentation on how to enable and work with GAC.

Existing Customers

The customers upgrading from the previous versions and enabling GAC must adhere to the given guidelines.

• Enabling the GAC changes existing permission model impacting existing entities and activities created in the previous version of Adeptia Connect. Therefore, it is recommended that the user first enables GAC in a non-production environment rather than enabling directly in the production environment.
• After enabling GAC, visibility of existing objects will remain the same because the standard roles (IT/Business/Admin) carry the same permission model.
• Also, the IT/admin users will be able to view option to create project and custom roles features on the UI after GAC has been enabled.

Access Management 

• The access control for IT users’ objects (Templates, Objects from Developer Studio, Process Flows, etc.) is based on Projects, therefore the user should manage all the objects through projects. Once you have enabled GAC, you must create the Project as desired through Projects option on Configure Tab.
• After creating the projects, it is highly recommended to arrange the objects in relevant projects as required.
  • While creating any template, you can select the Project, in which you want to create this template. 
  • Similarly, while creating any other entity i.e. Layout, Mapping, etc., you can define the project, in which you want to create the entity. 
• Likewise, the permission of Partner Entities (Networks, Partners, Transactions) will be controlled through Networks.

Role Creation

• After creating the projects, the user can create the roles and provide access to relevant projects or networks to specific role types.

• User can define a custom role and assign permissions to the new role as below:
  • Can Create Template, Can Invite Partner, etc.
  • Manage Project(s) on which the role has access. 
  • Manage the network on which the role has access. 

• After upgrading to v2.9.3 and enabling GAC, creating a transaction for Partner, the objects will not be filtered based on Partner’s Project. The objects will be filtered based on the project on which the user has permission. You can achieve this by visiting the Projects page in Connect.

For Users working on Adeptia Connect 2.9.2

Before enabling GAC, all the objects created by IT user remain in Project_1 by default*. 

* If the customer has applied Adeptia Connect v2.9.2 patch while creating a transaction for a Partner, the objects of only the following projects are displayed in the Layout and Mapping drop-down lists (not in Project_1 as mentioned above):

• • • • Partner’s Projects
      • Default Projects

Similarly, while creating a transaction for a Partner, if a user creates any objects such as Layout or Mapping, then these objects are listed within the Partner’s project (again, not in Project_1)

After you enable GAC in 2.9.3 patch, the above scenario will be rolled back to Project_1 mode.

Suggestions and Warning 

• GAC works on a fail-safe mechanism. Therefore, it is highly recommended not to disable this feature if you have created projects and entities using GAC permission model. Disabling GAC with entities created under projects can invite unknown consequences in already running transactions. 
• Also, Adeptia Connect does not support restore or reset option to the default settings of pre-GAC setup. Therefore, the user should enable only GAC only if the company has a requirement to manage access to Connect entities for various sets of users.

Get in touch with Adeptia support in case of any issues.