Return to main navigation Page
Data Columns are used to map attribute to document.
Attributes can only be mapped to the document under which they are
created. Data Column Mappings cannot have duplicates; an attribute can
be mapped to only one document.
Data Columns are used to create Process Manager Column
mappings. They are also useful in Reporting and Search because both
these functions can only be performed on data of attributes that have
been mapped in the data columns.
Each Commerce Process can have 251 Data Column mappings.
- 101 Data Columns are available for
main-document level Attributes (100 Data Columns and 1 Tab Column,
located on the Process Edit page).
- 150 Data Columns are available for sub-document level Attributes. These Data Columns can be mapped to sub-document Attributes or Configuration Attributes.
Adding a Data Column
- Navigate from the Admin Home Page > Commerce and Document > Process Definition > Select a Process > Data Columns > List.
- Click Addon the Mapping Data Columns page.
- Choose the Document(quote or line) to map an attribute to.
- Choose the Attribute to map to, based on the document selected in the previous step.
Set Default Parameters:
- Search Label:Enter the text label that should appear in any Search results.
- Report Label: Enter the text label that should appear on Reports, if enabled.
- Variable Name: Enter the variable name for the column. This cannot be changed.
If you return to edit at a later date, you'll see a list of where this data column is referenced. This includes Process Manager columns.
- Click Add to save your changes or click Cancel to return to the Mapping Data Columns page without saving your changes.
If you have made changes to Data Columns in
a process that has already been deployed, make sure to go to the
Deployment Center to repopulate column data.
Reordering Data Columns
- Specify the order number of the mapped data column on the Mapped Data Columns page.
- Click Apply.
- Click the Translations button on the Mapped Data Columns page.
Enter the translation for the Search Label and/or Report Label for each supported language.
- Click Save and Close to return to the Mapped Data Columns page.
Restricting Access for Data Columns
can be hidden from certain users or groups in Reporting, Search and the
Process Manager. The FullAccess user might choose to set up
permissions on data columns to ensure that sensitive information mapped
in the data columns is not visible to all users in Reporting, Search
and/or Process Manager.
- Click on the Restrict Access Icon for the selected data column. A dialog will appear.
Choose a company type from the Company Type drop-down who you want to be able to perform the Copy action.
- Choose a user type from the User Types drop-down who you want to be able to perform the Copy action.
- Click the greater than (>) sign button for moving the selected Company Type:User Types set to the Hide for following user type box.
- Remove a Company Type:User Types set from the
Access Rights list box by selecting the Company Type:User Types set and
clicking the lesser than (<) sign button.
- From the list(s) of internal/external groups, select the group(s) for whom you want to restrict access.
Move the user/group to the Hide for Following list(s).
- Click Save to save changes and remain
on the page. Click Save and Close to save changes and return to the
Mapping Data Columns page. Click Close to return without saving
To remove restricted access, simply select a user/group and click the button.
Deleting Data Columns
Admins have the ability to delete Data Columns without being required to undeploy the Commerce Process.
- Navigate from: Process Definition > Process > Data Columns - List
Select the Data Column you wish to delete by clicking its corresponding checkbox.
Warning messages will point users to any existing Column Mappings so dependencies can be removed.
Admins must re-populate data from existing columns, located in the Deployment Center.
Repopulate Column Data can be found in the
Deployment Center. This event ensures that any changes made in the Data
Columns on a deployed process are available on the commerce side. This
event is basically applicable for the transaction manager data
For Attributes selected for Tab Label in the Process Manager:
Tab Labels are always visible to every user even if
this attribute is mapped to a data column that is hidden from the logged
For Restricted Data Columns as Condition Filters in Reporting/Search:
Report/Search results are only run on the condition
filter attributes that the user has access to in the data columns. The
fullaccess user must be aware that shared reports/searches might yield
erroneous results for certain users if these users have been restricted
from data columns that are used as condition filters in the shared
Data columns cannot be deleted after they are created.