GAC is an add-on feature of Adeptia Connect. Therefore, you must check if your license supports this feature. Users can contact Adeptia Support for upgrading the license if this feature is unavailable. GAC is based on a role-based permission model. This section helps you differentiate how and what may change after you enable GAC.
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
However, 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*.
*However (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.
...
The Database Polling Service is used to check any changes in the data stored in a database table.
Prerequisites
- Database Info service must be created before creating Database Polling Service.
Steps to create a database polling:
Click Configure > POLLING > Database.
Click Create Database Polling.
- On the Create Database Polling window, enter the name and description of the new Database Polling service in the Name and Description fields.
- Select the Database Info service from the Database Info drop-down list.
- You can create the database event definition by entering an SQL Query or a database trigger command. By default, SQL Query option is selected. Enter the query in the SQL Query field. For example:
select * from PurchaseOrder where processingStatus='Ready'
Info Here:
processingStatus is a field in the source database table, which stores the status of the records. For example: If any record is already processed or not. This is important to make sure that same record should not be processed again and again.
You can use any existing field for this purpose or you can add an additional field.
In the above example, only those records, whose processingStatus is Ready, are picked for processing. - Select Check Condition checkbox if result of the selected query is to be compared with the conditional value.
- Select the operator for the query from the Operator drop-down list. Enter the value to be compared in the query in the Value field. The query should return only one record. If the query returns multiple records, then only the first record is accepted. If the query returns one record, then it will compare the value of the first field with the value specified in the Value field.
Alternately, enter the database trigger command in the SQL Trigger field.
Info Following is the format of SQL trigger.
<Trigger Text>
INSERT INTO dbpollingtable VALUES ('Query =<WHERE CLAUSE>');
END <trigger name> ;
Edit the parts, which are within < >. You can define a 'Where'
clause that indicates the row that is updated. When the command
is parsed, it will return the updated row from the database source.
Do not delete the Insert query.
<trigger name> after the END tag should be used for Oracle only.
In case of SQL server, <trigger name> is not needed.
Following is the example of the trigger used for SQL Server :
create trigger Trigger_test on emp for
insert,update
as
declare @empname varchar(20)
begin
set @empname=(select empname from inserted);
INSERT INTO dbpollingtable VALUES ('Query =WHERE empname='''
@empname'''');
END;
Following is the example of the trigger used for Oracle:
CREATE OR REPLACE TRIGGER Trigger_test AFTER INSERT OR
UPDATE ON Emp FOR EACH ROW BEGIN INSERT INTO dbpollingtable VALUES
('Query = where rowid= '||:new.rowid ); END Trigger_test;
Here :
Trigger_test is name of the trigger.
Emp is the name of the user table on which insert or updat
operation has to be done.
dbpollingtable is the name of the temporary table used. Do not
change it.- Enter the name of Trigger in the SQL Trigger Name field.
- Enter the time interval for Polling in the Polling Frequency field. Enter the digit in the Frequency field and select the unit of time i.e. seconds, minutes or hours etc. from the Duration dropdown list.
Enter the expiry time in the Expiry Time field. After expiry time process flow does not poll for data.
Info Adeptia recommends minimum Polling Frequency to be more than 60 seconds.
Info When a database polling service is used in a process flow, it creates a Polling Status activity variable. For more information, refer to Polling Status.
Expand the Advanced Properties section and select the Project from Project drop-down list.
- Click Save.
| Panel | ||||
|---|---|---|---|---|
| ||||
What's newBest practicesTraining guidesFrequently asked questionsAdeptia Connect APIsAdeptia security report |