B2B Integration 10.5 | Administering and Monitoring B2B Transactions | Trading Networks Administrator's Guide | Granting Access to Trading Networks | Granting Users Data Permissions | Granting Data Permissions to a Data Set
 
Granting Data Permissions to a Data Set
You must grant data permissions to act on a data set to at least one role.
When you grant data permissions to act on more than one data set to a role, the users belonging to that role get the data permissions granted in all those data sets. Be careful when assigning multiple data sets to a role, especially if one of the data sets contains the Exclude option for the partners, document types, or the processing rules. Trading Networks limits the partner profiles, TPAs, processing rules, transactions, document types, document attributes, tasks, and activity log entries in the data set based on the partners, document types, and processing rules you specify, as follows:
*For partner profiles and TPAs in the data set, access is based on and limited to the partners specified in the data set definition. For document types in the data set, access is based on and limited to the document types specified in the data set definition. For processing rules in the data set, access is based on and limited to the processing rules specified in the data set definition.
*For transactions in the data set, access is based on partners and document types specified in the data set definition, and is limited to transactions where both of the following are true:
*The sender or receiver of the transactions is associated with a partner specified in the data set.
*The transactions use a document type specified in the data set.
*For tasks (delivery and/or service execution) in the data set, access is based on the partners and document types specified in the data set definition, and is limited to tasks where both of the following are true:
*The receiver of the transaction is associated with a partner specified in the data set.
*The transaction uses a document type specified in the data set.
*For activity log entries, access is based on partners, document types, and processing rules specified in the data set definition, and is limited to activity log entries associated with the following:
*Events of transactions where the sender or receiver is associated with a partner specified in the data sets, and these transactions use a document type specified in the data set.
*Profile administration audit trails of partners specified in the data set.
*Document type audit trails of document types specified in the data set.
*Processing rule audit trails of processing rules specified in the dataset.
*Activity logs that are not associated with any of the transactions, document type administration audit trails, processing rule administration audit trails, or profile administration audit trails.
* To grant data permissions to a data set
1. In My webMethods: Administration > System-Wide > B2B Permissions > Data Permissions.
2. In the Data Set Name column, click the data set to which to grant data permissions.
3. Click the Permissions tab.
4. To add a role for the data set, click Add Role and do the following:
a. In the Select Roles dialog box, type a string that exists in the names of the roles to add and click Search.
b. Move the roles to which to grant data permissions from the Available list to the Selected list.
c. Click Apply.
5. To grant data permissions to a role:
a. Click Edit icon in the row that contains the role to which to grant data permissions.
b. In the Edit Permissions dialog box, select the check boxes for the permissions to assign to the role and clear the check boxes for the permissions you do not want the role to have. Most data permissions are self-explanatory. Permissions that require additional explanation are covered below.
Note: Only administrators can perform actions on the Enterprise profile.
Data Permission
Notes
Create Profile
Edit Profile Summary and Edit External IDs are granted automatically after you save and re-open the data set.
Note: By default, profiles created by this user are added to all data sets to which the user has this permission. If the data set has the All Partners option selected, the profile of the partner will always belong to that data set, and the My webMethods+ user does not need to explicitly add it to the data set.
View Transactions
View Profile, View Document Type, and View Document Attributes are granted automatically.
View Activity Log
View Profile and View Document Type data are granted automatically.
View Task
View Profile and View Document are granted automatically.
Create Document Types
View Document Types data permission is granted automatically.
Note: By default, document types created by this user are added to all data sets to which the user has this permission. If the data set has the All document types option selected, the new document types will always belong to that data set, and the user need not explicitly add it to the data set.
View Document Types
View Document Attributes data permission is granted automatically.
Manage Attributes
View, create, edit, enable, and disable document attributes.
Create Trading Partner Agreements
Includes permission to delete TPAs.
Create Processing Rules
Includes permission to delete processing rules.
Note: By default, processing rules created by this user are added to all data sets to which the user has this data permission. If the data set has the All processing rules option selected, the processing rule of the partners will always belong to that data set, and the user need not explicitly add it to the data set.
Manage Partner Access to APIs
Add APIs and view APIs data permissions are granted to manage API access to partners.
Note: Even if a user does not have the Create Document Types data permission to a particular document type, Trading Networks might list that document type in search results or as related documents in some My webMethods pages. However, the user will not be able to view or edit the details of the documents without those data permission.
Copyright © 2016- 2019 | Software AG, Darmstadt, Germany and/or Software AG USA, Inc., Reston, VA, USA, and/or its subsidiaries and/or its affiliates and/or their licensors.