Glossary
-
The term used to indicate the drive selected for EnterWorks use is <drive> such that a file path of D:\Enterworks\logs is written as <install drive>:\Enterworks\logs. Additional terms include <install-drive> and <installation directory>.
-
EnterWorks services use the <network_service_account> to log in. This account needs full control of all EnterWorks folders and any shared folders, as does each admin user and admin group that will manage the application. A commonly used name for this account is "ewservice".
-
Active Directory is a Microsoft application hosted on an Active Directory server. It manages user passwords and performs user authentication.
-
The contents of a Repository View can be filtered by attribute values. Selecting an attribute value to use as filter causes an Active Filter box to be displayed in the Active Filters Bar that indicates the name of the attribute and what filter is being applied to its values.
-
The Active Filters bar appears in a Repository View. It indicates any Active Filters.
-
Workflow: The label given to an activity in a process flow.
-
Workflow: The role or user that performs the work associated with a given activity in a process flow.
-
An Advanced Saved Search (sometimes also called an Advanced Search) allows the user to create an Active Filter based on a repository’s attribute value, the state of its records, a linked repository’s attribute values, or the repository’s owner.
-
Workflow: A specific actor is assigned to a role type and receives all work items related to that role.
-
Workflow: A point in a process flow where a single thread of control splits into two or more parallel paths. Work item versions are always sent to all destinations of the split.
-
Workflow: A point in a process flow where two or more parallel executing activities converge into a single common thread of control and are synchronized
-
Application Programming Interface
-
An application is a set of functional capabilities based on a set of sources, specifications, scenarios, and scripts.
-
An association group is a set of attributes that coordinate with each other, in that each attribute field consists of a list of values, where the first value in the list of one attribute relates to the first value in the list of the other attributes in the association group. For example, the association group could have the attributes “Country”, “Tariff”, “Currency”, and “Measurement”. The attribute values for a record might be: Country = Argentina | Germany | India | United States Tariff = 0.02 | 0.04 | 0.06 | 0.08 Currency = peso | euro | rupee | dollar Measurement = metric | metric | metric | USCS Where for the Country “Argentina”, the Tariff is “0.02”, Currency is “peso”, and the Measurement system is “metric”.
-
An association object is used to assign category attributes to the taxonomy and to assign dynamic attributes to a specific control attribute. It is a list of control attribute values and their assigned category/dynamic attributes. There is one [control-attribute-value | category/dynamic-attribute] pair for each attribute assigned to a control attribute. In the case of category attributes (which are controlled by the taxonomy) and dynamic attributes that are controlled by a hierarchy attribute, the association object also indicates if an attribute for a node can be inherited by its children nodes, meaning that the attribute is assigned once to the parent node but also applies to all its children nodes.
-
An Attribute is a field in a record that stores information about the item defined in the record, such as the item’s price or color. It is a database table’s column.
-
Records may have thousands of attributes, which can make them unwieldy to view or edit. For display purposes, attributes are grouped, typically according to their function. For instance, all the metric measurement attributes might be placed into a group called “Metric Measurements” and the imperial measurements in a group called “Imperial Measurements”. These attribute groups are then placed into larger groups called attribute tabs. The groups Metric Measurements and Imperial Measurements might be placed into a tab named “Specifications”. When a record is opened in an editor, the attribute tabs are displayed. The tabs can be expanded to show the attribute groups. The attribute groups can be expanded to show the actual attributes themselves. Each repository has its own set of attribute tabs and groups. Attribute tabs and groups are defined and maintained by the system administrator.
-
Determines which of a repository’s attributes may be read or edited. Defining security for a repository consists of granting access permissions to user groups for the records and attributes the security filters have made available for reading and editing. Attribute security filters list which attributes are available to be read or edited. If a repository’s security settings do not specify an attribute security filter, the default filter will be used and no attributes will be visible – no users will be able to see any data in that repository.
-
Records may have thousands of attributes, which can make them unwieldy to view or edit. For display purposes, attributes are grouped, typically according to their function. For instance, all the metric measurement attributes might be placed into a group called “Metric Measurements” and the imperial measurements in a group called “Imperial Measurements”. These attribute groups are then placed into larger groups called attribute tabs. The groups Metric Measurements and Imperial Measurements might be placed into a tab named “Specifications”. These attribute groups are then placed into larger groups called attribute tabs. The groups Metric Measurements and Imperial Measurements might be placed into a tab named “Specifications”. When a record is opened in an editor, the attribute tabs are displayed. The tabs can be expanded to show the attribute groups. The attribute groups can be expanded to show the actual attributes themselves. Each repository has its own set of attribute tabs and groups. Attribute tabs and groups are defined and maintained by the system administrator.
-
An auto-sequenced attribute field is similar to a calculated field. Upon the creation of a record, EnterWorks’s auto-generate sequence feature will automatically generate a unique value for the auto-sequenced attribute field. Each repository profile may have one attribute that is defined as auto-sequencing; typically this would be its primary key or an item number. At the time of record creation, the user may be allowed to enter the value of an auto-sequenced field (depending on the configuration of EnterWorks). When the record is saved for the first time, if the user is allowed to set a value for that field, its value will be saved. If not, EnterWorks will generate the field value based upon the next number in the sequence and any configured rules. Once the new record is saved, unless EnterWorks is configured differently, the value of the auto-sequenced field cannot be changed.
-
An auto-sequenced attribute field is similar to a calculated field. Upon the creation of a record, EnterWorks’s auto-generate sequence feature will automatically generate a unique value for the auto-sequenced attribute field. Each repository profile may have one attribute that is defined as auto-sequencing; typically this would be its primary key or an item number. At the time of record creation, the user may be allowed to enter the value of an auto-sequenced field (depending on the configuration of EnterWorks). When the record is saved for the first time, if the user is allowed to set a value for that field, its value will be saved. If not, EnterWorks will generate the field value based upon the next number in the sequence and any configured rules. Once the new record is saved, unless EnterWorks is configured differently, the value of the auto-sequenced field cannot be changed.
-
When used in relation to Workflow: A representation of the action that a BIC performs in a process flow
-
EnterWorks will request that the IDP authenticates users and manages their user group assignments. When an existing EnterWorks user logs into EnterWorks, EnterWorks will verify with the IDP that the user exists in the IDP's directory and it will request a list of the groups the user belongs to. For each group on the returned list that exists in EnterWorks, if the user is not in the group, EnterWorks will add them. EnterWorks will then remove the user from any EnterWorks groups that are not on the list returned from the IDP.
-
The simplest search is a Basic Text Search. For this search, the user enters text into the Text Search box on the far left of the Tab Bar. EnterWorks searches the current view to find any occurrences of the search term. The search term becomes a Filter.
-
Business Integration Component. An independent program used to integrate data, files, and messages from external file systems and third- party applications, and to automate activities in a process.
-
A calculated field is an attribute whose value is determined by the values of other attributes or system variables. For instance, the value of the attribute “Area of Rug” might be calculated by multiplying the value of the attribute “Rug Length” by the value of the attribute “Rug Width”. The values of calculated fields are not determined until the record is saved, both in the case of a new record being added and when an existing record is being edited. If a user edits a value in a calculated field, depending upon system configuration it may be overwritten with the system-derived value when the record is saved.
-
Some attributes are relevant for only a subset of records in a repsoitory, in contrast to global attributes that apply to all records in a repository. EnterWorks can be configured to define these relevant attributes as category attributes (also known as category-specific attributes). Category attributes are assigned to a taxonomy node, which indicates to EnterWorks that all the records attached to that node use those attributes. The taxonomy attribute is the control attribute for category attributes. Depending on system configuration, descendent taxonomy nodes (a node’s subcategory nodes or children nodes) can inherit category attributes as well. Note that category attribute values are not shared – each record still maintains its own attribute value. The only effect of designating an attribute as a category attribute is to indicate to EnterWorks which attributes are relevant for a particular record.
-
Some attributes are relevant for only a subset of records in a repsoitory, in contrast to global attributes that apply to all records in a repository. EnterWorks can be configured to define these relevant attributes as category attributes (also known as category-specific attributes). Category attributes are assigned to a taxonomy node, which indicates to EnterWorks that all the records attached to that node use those attributes. The taxonomy attribute is the control attribute for category attributes. Depending on system configuration, descendent taxonomy nodes (a node’s subcategory nodes or children nodes) can inherit category attributes as well. Note that category attribute values are not shared – each record still maintains its own attribute value. The only effect of designating an attribute as a category attribute is to indicate to EnterWorks which attributes are relevant for a particular record.
-
Channel readiness is a measure of how ready a channel is to be syndicated to its target, that is to say, how many of the required record attribute values have reached a validation level sufficient to be syndicated to their target.
-
A code set is a special data type that consists of a list of predefined value pairs, “Code” and “Description”, that contain all possible values for the attribute. When the attribute is displayed for editing by the user, the user will be presented with the list of paired values to choose from. If the Code and Description values are the same, only the Code will be displayed. If the Code and Description are different, they will be displayed as “<Code Value> -- <Description Value>”.
-
A comparison function compares a column's value in two records and determines the likelihood that the values match.
-
The composite score of comparing two records is computed as a sum of the column comparisons scores for the given columns, divided by the number of columns. This value is specified as a percentage ranging from 0 to 100
-
The final record whose values are computed by applying the consolidation rules to matched records.
-
The final value for a consolidated record's column. It is computed by applying a survivorship function to the set of values from matched records.
-
Consolidation rules define how to compile a consolidated (merged) record from a set of matched (duplicate) records.
-
A term used to specify the work area in a window such as the large area on the right hand side of the Design Console, TaskManager, and Report Tool.
-
Some attributes are relevant for only a subset of records in a repsoitory, in contrast to global attributes that apply to all records in a repository. EnterWorks can be configured to define these relevant attributes as category attributes (also known as category-specific attributes). Category attributes are assigned to a taxonomy node, which indicates to EnterWorks that all the records attached to that node use those attributes. The taxonomy attribute is the control attribute for category attributes. Depending on system configuration, descendent taxonomy nodes (a node’s subcategory nodes or children nodes) can inherit category attributes as well. Note that category attribute values are not shared – each record still maintains its own attribute value. The only effect of designating an attribute as a category attribute is to indicate to EnterWorks which attributes are relevant for a particular record.
-
Correction Files indicate the validation status of a repository's attribute values. They are generated when record validation is performed manually by the user.
-
The Digital Asset Manager (DAM) is the set of folders, repositories, and processes used to store digital assets and make them accessible to the rest of EnterWorks.
-
A measurement of the validity of an enterprises' data and the data's readiness for syndication.
-
A repository’s Default Preference is the view used when the repository is first opened in a Repository View.
-
A record attribute may be configured to have a default value. When a new record is added, any attribute that has a specified default value will be set to the default value. Depending on the way the attribute was defined, the user or the system may be allowed to change the value.
-
The Digital Asset Manager (DAM) is the set of folders, repositories, and processes used to store digital assets and make them accessible to the rest of EnterWorks.
-
An organization's Digital Assets are files used in relation to the data being managed, such as digital images, audio files, video files, PDF documents, Microsoft Office documents, and other file types. The DAM is the set of folders, repositories, and processes used to store digital assets and make them accessible to the rest of EnterWorks.
-
Two options exist to store the properties of a data model object: -- Properties Repository: (Preferred.) A repository that is created to hold the data model object’s properties, then it is attached to the data model object. A properties repository is more flexible and easier to access than directly-attached properties. -- Directly-attached Properties: (Non-preferred.) Properties are added directly to the object definition. These are more ridged and harder to change and adapt over time than properties repositories. The benefits of creating a properties repository is that the properties can be managed, imported and exported more easily, in the same manner that other repositories are rather than the user having to edit the data model object.
-
Workflow: The box containing a list of work items that have been created, but not yet introduced into a process flow.
-
During configuration, the system administrator can select specific attributes in a repository to be drill-down indexes. When the user opens the Filter Sidebar, a list of the drill-down index attributes appear. Upon the user expanding a drill-down index attribute, a list of all the values that attribute has in the repository is displayed. Each attribute value displays a count of how many times that attribute value appears in the repository.
-
Delivery Service Notification
-
Dynamic attributes are like category attributes, but they can be assigned to a control attribute that is not the taxonomy. The control attribute for category attributes is the taxonomy attribute and only the taxonomy attribute, so a repository can only contain one set of category attributes. Since dynamic attributes are assigned to other attributes, a repository can have more than one set of dynamic attributes. If the control attribute for a set of dynamic attributes is a hierarchy attribute, dynamic attribute values can be inherited.
-
Editor controls specify how an attribute value is displayed and the format the user will use to enter that value. These specifications are not determined by the attribute’s data type, but by how the attribute value will be used. For instance, although an attribute that holds a phone number might have the data type of VARCHAR and a length of 10, an editor control rule for that attribute may denote that the editor will display the phone number as “(xxx) xxx-xxxx” and that as the user types in digits, they will be composed in that format.
-
Enterprise JavaBeans
-
Workflow: A work item that has been introduced into a process flow but has not yet reached its final destination activity in the process flow.
-
An EnterWorks system typically consists of three separate environments: DEV, QA, and PROD. The data model is developed in the DEV environment, tested in the QA environment, and put into production in the PROD environment.
-
EnterWorks Process Exchange. An object-oriented, Java-based automation tool that extends process flow technology to business processes task.
-
The Events function allows the user to specify changes to a set of records that will occur at a later date and time. Optionally, the user may specify an expiration date for the changes, after which the records will revert to their state before the Event was defined.
-
The Favorite Detail Editor Preference defines how record data will be displayed in the Inline Editor and the Detail Editor.
-
In a Repository View, the Filter Sidebar displays the list of drill-down index attributes available to filter the list of records shown. Upon the user expanding an index attribute, a list of all the values that attribute has in the repository is displayed. Each attribute value displays a count of how many times that attribute value appears in the repository.
-
Filters provide a way for the user to quickly find a set of records based on the values of selected attributes.
-
Workflow: A tag name within a form tag on an HTML page, which appears as an option in a work item viewer.
-
User accounts are configured in EnterWorks, then the users are assigned to user groups. To efficiently manage system security, EnterWorks recommends it is managed at the group level, therefore groups should be defined according to user roles, such as Administrator, Product Manager, Publications Manager, or Syndication Manager. During configuration, groups are analyzed and designed to align with an organization’s specific business processes and operational requirements.
-
A hierarchy is similar to a taxonomy. Both are tree-like structures; however, a hierarchy interacts with product records differently. A hierarchy is used to define a navigational path to one or more records. A record can belong to one or more hierarchies. The node assignments are stored in a separate repository, to allow each record to be assigned to multiple hierarchy nodes. This allows the record to be found in more than one category during a search. An example would be record for an “Abrasive Disk” item that was ssigned to a category node called “Abrasives” and a category node of “Power Tool Accessories”. Records can be assigned to multiple nodes from multiple Hierarchies. Hierarchies cannot have category attributes. A hierarchy is similar to a taxonomy. Both are tree-like structures; however, a hierarchy interacts with product records differently. A hierarchy captures a path that someone might follow to find a product record.
-
A taxonomy path or hierarchy path is the route traversed from the root node to get to the assigned node. It is often called “a node’s taxonomy” or “a node’s hierarchy”. It is stored as a string of characters.
-
An input field defined in an HTML form.
-
Workflow: A work item that is viewed using an HTML form IIOP Internet Inter-ORB Protocol.
-
A list of pending work items assigned to a user Java An object-oriented, cross-platform programming language developed by Sun Microsystems specifically for use on the Internet.
-
Depending on system configuration, descendent taxonomy nodes (a node’s subcategory nodes or children nodes) can inherit category attributes. Note that category attribute values are not shared – each record still maintains its own attribute value.
-
A full-featured, platform-independent, extensible help system for incorporating Help into applets, components, applications, operating systems, and devices. Allows EPX users to view the product documentation.
-
Java Database Connectivity
-
Java Development Kit
-
Job scheduling is the function that allows the user to pre-schedule a one-time activity or repeated activities.
-
Workflow: An activity in a process flow where two or more parallel activities converge into a single common thread of control.
-
A join attribute pair is used to identify linked records. You need to have a dedicated attribute in the child repository that will be used to identify the parent record so that EnterWorks knows which child records have which parents. When a child record is created, its join attribute value will be set to the parent’s join attribute value.
-
EnterWorks will request that the IDP authenticates users and manages their user group assignments. When an existing EnterWorks user logs into EnterWorks, EnterWorks will verify with the IDP that the user exists in the IDP's directory and it will request a list of the groups the user belongs to. For each group on the returned list that exists in EnterWorks, if the user is not in the group, EnterWorks will add them. EnterWorks will then remove the user from any EnterWorks groups that are not on the list returned from the IDP.
-
Java Virtual Machine. The program responsible for processing Java applications.
-
Lightweight Directory Application Protocol. A type of protocol used for Single Sign-On (SSO).
-
Secure LDAP, also known as LDAP over SSL. A type of protocol used for Single Sign On (SSO).
-
Linked records are records that have a relationship with another record. For example, a product record may contain links to accessory products or related products. The records can be in the same repository or in different repositories. Link relationships can be “one-to-one” (one record linked to anotherrecord), “one-to-many” (one record linked to more than one record), or “many-to-many” (records can both have more than one record link to them and can link to more than one record). A repoistory that contains records linked to another repository may be referred to as a "linked repository".
-
Linked records are records that have a relationship with another record. For example, a product record may contain links to accessory products or related products. The records can be in the same repository or in different repositories. Link relationships can be “one-to-one” (one record linked to anotherrecord), “one-to-many” (one record linked to more than one record), or “many-to-many” (records can both have more than one record link to them and can link to more than one record). A repoistory that contains records linked to another repository may be referred to as a "linked repository".
-
If local user authentication is used, an EnterWorks system administrator uses EnterWorks to manage user passwords. EnterWorks performs all user authentication.
-
When used in relation to Workflow: A representation of the action that a user performs in a process flow.
-
A match column is a column used in the matching process to determine if records are duplicates.
-
If the comparison of two values or records generates a score greater than or equal to the match cutoff value, the values or records are declared a match.
-
Match rules define the conditions that must exist for records to be declared duplicates.
-
When used in relation to Workflow: An application used to migrate information from one EPX server to another.
-
When used in relation to Workflow: The area or window that allows users to select or move through various elements of the Design Console, TaskManager, and Report Tool.
-
Objects are any of Fusion's basic components: sources, specifications, scenarios, operations, scripts, and applications.
-
When used in relation to Workflow: Classifications of the EPX-specific data stored in the EPX database, such as process flows and their components
-
Open Database Connectivity
-
Workflow: A point within a process flow where a single thread of control splits into two or more parallel activities. Only one activity receives a work item.
-
Operations implement basic data integration tasks. For example, the LoadTableFromSource operation loads any table from any data source into another data source. Operations are called from scenarios.
-
When used in relation to Workflow: A point within a process flow where two or more alternative activities’ branches re-converge to a single common activity as the next step within the process flow. As no parallel activity execution has occurred at the join point, no synchronization is required. This type of join requires that each work item be released back into the process flow when completed.
-
An orphan is a digital asset file that does not have a record in DamMaster or a record in DamMaster that does not have a link to a digital asset file.
-
The viewer configured to display a work item’s contents at a specific activity.
-
Records are modified in the Staging environment and then moved to Production using the promotion process. Promotion can be handled automatically or manually, depending on system configuration. A package is a group of records from linked repositories. If a repository is designated as package-dependent, none of its records will be promoted to Production if any of the records in the package have severe validation errors. If a repository is not designated as package-dependent, its valid records will be promoted to Production even if the packages containing them are deemed invalid.
-
Records are modified in the Staging environment and then moved to Production using the promotion process. Promotion can be handled automatically or manually, depending on system configuration. If a repository is designated as package-dependent, none of its records will be promoted to Production if any of the records in the package have severe validation errors. If a repository is not designated as package-dependent, its valid records will be promoted to Production even if the packages containing them are deemed invalid.
-
In Workflow, one or more users or groups of users.
-
Multiple actors are assigned to a single activity, allowing all actors in a group (pool) to view any work items that are sent to the activity
-
In order to insulate “production-ready” data from updates that may be incomplete or invalid, EnterWorks supports the creation of separate Staging and Production versions of the data. They are called Staging and Product environments. Records are stored in the Staging and Production environments depending on their readiness for use. Production repositories holds records that are ready for use: they have been validated and are available for internal use or export. Staging repositories holds records that are in the process of being populated or validated. Staging is thought of as a work area. Some organizations also havetemporary Pre-staging repositories for records that are not yet ready for Staging. Pre-staging is typically used for imported data that needs processing or validation before it is ready for Staging.
-
To prefer a record means to specify a strategy to declare one of record in a set of matched records to be the primary record, then use its values as the consolidated values.
-
Creating a Preference (sometimes referred to as a Preference View) allows users to design a particular view of a repository's contents when the repository is open in a Repository View.
-
Each record in a repository has a unique record ID attribute called a key. The record’s unique, identifying key is called its primary key. Primary keys are often auto-generated.
-
The area where a process flow is graphically defined
-
A process flow or subflow layout that can be used as a basis for creating new process flow or subflow processes
-
The flow of information and control in a business process
-
In order to insulate “production-ready” data from updates that may be incomplete or invalid, EnterWorks supports the creation of separate Staging and Production versions of the data. They are called Staging and Product environments. Records are stored in the Staging and Production environments depending on their readiness for use. Production repositories holds records that are ready for use: they have been validated and are available for internal use or export. Staging repositories holds records that are in the process of being populated or validated. Staging is thought of as a work area. Some organizations also havetemporary Pre-staging repositories for records that are not yet ready for Staging. Pre-staging is typically used for imported data that needs processing or validation before it is ready for Staging.
-
A Profile defines the structure (schema) of records in one or more repositories. The profile determines which attributes (data items) a repository will store for each record, the data type of each attribute, and the order the attributes are stored in the record. A profile may be used to define multiple repositories.
-
Profile attribute properties: The attribute properties defined at the profile level. These provide the initial values of the repository attribute properties when a new repository is created based on that profile. When a repository is created, the values of its profile’s attribute properties are copied into its repository attribute properties. Changing the profile’s attribute properties does not change the repository attribute properties for any existing repositories based on that profile.
-
Records are modified in the Staging environment and then moved to Production using the promotion process. Promotion can be handled automatically or manually, depending on system configuration.
-
Properties are metadata attached to a data model object, such as a default value for an attribute.
-
Two options exist to store the properties of a data model object: -- Properties Repository: (Preferred.) A repository that is created to hold the data model object’s properties, then it is attached to the data model object. A properties repository is more flexible and easier to access than directly-attached properties. -- Directly-attached Properties: (Non-preferred.) Properties are added directly to the object definition. These are more ridged and harder to change and adapt over time than properties repositories. The benefits of creating a properties repository is that the properties can be managed, imported and exported more easily, in the same manner that other repositories are rather than the user having to edit the data model object.
-
A record is storage for information about one item in a repository; a database table’s row.
-
Record Security Filters and Attribute Security Filters determine which of a repository’s attributes and records may be read or edited. Defining security for a repository consists of granting access permissions to user groups for the records and attributes the security filters have made available for reading and editing. Record security filters return only the records that match their search conditions. The use of record security filters is optional. If a record security filter is not applied, the default record security filter returns all records. Repository security consists of defining: for the set of records the record security filter returns, and the attributes made visible by an attribute security filter, what access permissions are assigned to particular user groups. Security for profiles, code sets, hierarchies, and taxonomies does not use attribute and record security filters. User groups are directly assigned permissions.
-
The process of validating the attribute values of a record according to validation levels and validation rules.
-
A Web-based application used to obtain reports on the status of business processes implemented within EPX
-
A repository is a storage for a collection of data; a database table. A repository holds only one type of information.
-
Repository attribute properties are the properties of the attributes in a repository. These are managed at the repository level, so a repository’s attribute properties are distinct and separate from another repository’s attribute properties, even if the repositories are based on the same profile.
-
Repository Properties: The properties of a repository, such as whether a repository’s valid records are automatically published. Repository properties are managed at the repository level, so each repository’s properties are distinct and separate from the properties of other repositories, even if they are based on the same profile.
-
A Repository View is a display of the contents in a repository.
-
A restricted hierarchy is similar to a taxonomy. An attribute in the repository is used to store a record’s hierarchy node assignment, so a record can only be assigned to one node in the hierarchy. However, the record can be assigned to nodes in multiple hierarchies. Each hierarchy’s node assignment is stored in its own repository attribute. Restricted hierarchies cannot have category attributes.
-
Remote method invocation
-
Represents a function in a process flow that can be assumed by one or more users. Typical roles might be “supervisor” or “administrator”.
-
When a split occurs in a process flow, a routing slip appears in TaskManager where a user specifies which activity (One split) or activities (Some split) to send the work item to
-
The Saved Search functionality allows the user to search the contents of a repository and save the search for later use. A Saved Search may also be shared with other users.
-
A Saved Set is a group of one or more records in a repository. Each Saved Set has a unique name and can be stored for later use. Saved Sets can be used to revisit the same group of records without having to search for them again. Saved Sets contain records from only one repository. A repository can have many Saved Sets. Saved Sets can also be shared so all other users can see and use them.
-
A scenario is a procedure that consists of a sequence of operation calls. Scenarios are the basic mechanisms used to perform operations on data sources.
-
A specific actor works all activities assigned to a specific role during a specified period of time
-
The Scheduled Jobs repository contains records representing the currently active and recently completed jobs. When a job is initiated, a record for the job is created in the scheduled jobs repository. The details of the job are copied to the record and the record is subsequently updated to reflect the current status of the job.
-
A scheduling repository stores the configuration details for each instance of an activity; one record per each defined activity. Configuration details might include which template to use, transmission options, how often to perform the activity, etc.
-
Scripts contain queries or scripts written in a source-specific language, for example, a SQL query to be used on a PosgreSQL database.
-
A request to send a work item to the next destination in the process flow
-
The user or BIC that requests a work item to be sent
-
The list of work item versions that have been acted on by a particular user or role.
-
Each record in a repository needs a unique ID to identify it. These IDs are tracked via a sequence object (also called a sequence or sequence definition), which keeps track of the IDs that have been used in that repository.
-
Each record in a repository needs a unique ID to identify it. These IDs are tracked via a sequence object (also called a sequence or sequence definition), which keeps track of the IDs that have been used in that repository.
-
A record’s primary key is not to be confused with its sequence number. A sequence number only describes the order in which records are displayed in a Repository View. It is not used to identify the record.
-
Each record in a repository needs a unique ID to identify it. These IDs are tracked via a sequence object (also called a sequence or sequence definition), which keeps track of the IDs that have been used in that repository. A sequence can be shared by multiple repositories, which would guarantee that each record has a unique id across all the repositories using that sequence. A use for this would be if products were being entered in multiple repositories but each product needed a unique product ID. Although a sequence definition can be shared by multiple repositories, it is recommended as best practice to create a separate sequence definition for each repository. The default sequence object is commonly used if the user doesn’t care what the sequence numbers are as long as they uniquely identify each record.
-
A small, pluggable Java extension to a server that enhances the server’s functionality. Servlets are used in EPX to provide dynamic content for TaskManager and to provide access to Report Tool.
-
Shared configuration properties are system configuration values that are used across all servers in an EnterWorks installation, such as file paths, security settings, etc.
-
If users will be accessing an attribute frequently for searches in the repository, adding it to to the Snapshot table and designating it as a database index can improve system perfomance significantly.
-
A Snapshot Table is a database table that is used to store attribute values that need to be accessed quickly.
-
A point within a process flow where a single thread of control splits into two or more parallel activities. One or more destinations can receive a work item.
-
A source (also known as a data source) is a named collection of spaces.
-
A space is a named collection of tables. For example, a set of schemas in a PostgreSQL database is represented as a space in the Fusion UDM.
-
A specification is the rules for a data integration task. For example, the Matching specification type contains rules to find and consolidate duplicate records in a table. Each specification has a name, a type, and a list of type-specific parameters.
-
A point within a process flow where a single thread of control splits into two or more parallel activities. Depending on the type of split, work items are sent to one, some, or all destination activities.
-
Structured Query Language
-
Secure Sockets Layer
-
Single Sign-On.
-
In order to insulate “production-ready” data from updates that may be incomplete or invalid, EnterWorks supports the creation of separate Staging and Production versions of the data. They are called Staging and Product environments. Records are stored in the Staging and Production environments depending on their readiness for use. Production repositories holds records that are ready for use: they have been validated and are available for internal use or export. Staging repositories holds records that are in the process of being populated or validated. Staging is thought of as a work area. Some organizations also havetemporary Pre-staging repositories for records that are not yet ready for Staging. Pre-staging is typically used for imported data that needs processing or validation before it is ready for Staging.
-
An activity within a process flow in which work items can be introduced.
-
When a record is opened in an editor, attributes selected as summary attributes are displayed in the record header. Any attributes may be selected to be summary attributes, even attributes in records that are linked from another repository.
-
For a set of matched records, a survivorship function is used to determine which record's value will be used in the final merged record.
-
Syndication is the process of exporting Production data to a particular syndication target, (user of the data).
-
A syndication channel is a data stream consisting of a set of data being transmitted (or made available to) a particular syndication target.
-
Syndication is the process of exporting Production data to a particular target, (user of the data). Syndication targets may include targets such as web pages, servers that process product orders, or subsidiary businesses. A syndication channel is a data stream consisting of a set of data being transmitted (or made available to) a particular syndication target.
-
A table schema is an ordered list of columns that defines the structure of a table and all its records.
-
When used in relation to Workflow: A Web-based application that allows process flow users to access the work items they are assigned to.
-
A taxonomy describes the path from the root to the node a product record is attached to. Every product record has a taxonomy. Taxonomies are typically written as: root.node.node…last_node (though they can be written in other formats, depending on the configuration of EnterWorks).
-
A taxonomy node property is metadata that applies to a taxonomy node. It describes a characteristic of records assigned to that node. For instance, a property field might be used to hold the name of the department responsible for records attached to the node, or it might indicate if the records attached to the nodes are product records.
-
A taxonomy path or hierarchy path is the route traversed from the root node to get to the assigned node. It is often called “a node’s taxonomy” or “a node’s hierarchy”. It is stored as a string of characters.
-
A character that indicates the delimiter character should be processed as a character, not a delimiter. It is placed before and after a string that contains the delimiter character. If the text qualifier appears twice in a row, it indicates that it is to be processed as a character, not a text qualifier. For example, if the delimiter is a comma , and the text qualifier is a double quote " then the value: ,”3”” x 4””, Rough Cut” would be stored as: 3” x 4”, Rough Cut.
-
When used in relation to Workflow: The path between two activities in a process flow with an origin at the source activity and a termination at the destination activity.
-
A graphical representation of a transition in a process flow between two activities. It consists of a line with an arrow pointing to the destination activity.
-
A transmission option is an object that defines the method of transmitting an exported file to a destination. A transmission option can be used by more than repository. A transmission option object maintains a different set of configuration settings depending on the type of transmission option. Transmission options store information such as the protocol used, modifications to the resulting file name, file destination, and any necessary destination-imposed user authentication.
-
A tree structure is a type of categorization of data into categories and subcategories. Think of starting at the root (or trunk) of the tree – that’s the main category, for instance: Party Goods. From the root, the data branches into subcategories: Balloons, Tableware, and Decorations. Then Balloons splits into subcategories: Mylar and Latex. The point where a category splits is called a node and so are the final subcategories (the ends of the branches). The actual products themselves (the item records) are assigned to nodes. Every record is assigned to one, and only one, node. Nodes can have multiple records assigned to them.
-
User accounts are configured in EnterWorks and then the users are assigned to user groups. To efficiently manage system security, EnterWorks recommends it is managed at the group level, therefore groups are defined based on system responsibility roles, such as Administrator, Product Manager, Publications Manager, or Syndication Manager. During configuration, groups are analyzed and designed to align with an organization’s specific business processes and operational requirements.
-
The attribute values of a record are validated when attribute values are entered into the system. This typically occurs when a record is imported into the database, or when the user creates a new record or opens an existing record in the Detail Editor, edits and saves it. Attribute values are checked against constraints placed by the data type, editor control settings, and explicit validation rules. The constraints are independent of validation levels (i.e., they are always applied). Validation rules can be assigned to specific validation levels.
-
The use of validation levels gives an organization the ability to determine if particular validation errors and warnings are severe enough to prohibit the syndication of a record to a particular target. They allow a record to be deemed good enough for syndication to one target but not another. Validation levels are associated with the quality of the record’s attribute values. Validation rules are assigned to validation levels; for a record to reach a level of validation, it must pass the validation checks for that level and all the validation levels beneath it.
-
The attribute values of a record are validated when attribute values are entered into the system. This typically occurs when a record is imported into the database, or when the user creates a new record or opens an existing record in the Detail Editor, edits and saves it. Attribute values are checked against constraints placed by the data type, editor control settings, and explicit validation rules. The constraints are independent of validation levels (i.e., they are always applied). Validation rules can be assigned to specific validation levels.
-
A record’s validation status indicates whether it achieves its assigned validation level.
-
When used in relation to Workflow: That portion of TaskManager that uses an HTML file to display work items in a particular format
-
When used in relation to Workflow: A work item viewer can be associated with a given work item type. This association indicates which HTML forms can be used to view a work item of a given type.
-
When used in relation to Workflow: A Uniform Resource Locator to an HTML file. In EPX, it must be specified relative to the server URL.
-
Workflow: A work item is a marker for a specific job that is going through the process. The work item contains information about the job and where the job is in the process.
-
An instance of the data that represents a work item at a given activity in a process flow. Also called work item version.
-
A label assigned to a work item.
-
An abstract category used to classify work items, denoted by a name, such as Time Sheet.
-
An HTML file displayed by TaskManager that represents a view of the data contained in a work item version.
-
An electronic document or other form of data passed in a process flow.
-
A workflow is a business process. It is a set of tasks that must be performed to fulfill a function.
-
Extensible Markup Language. Allows you to define your own set of tags to define data, thereby defining the logical structure of the data.
-
Extensible Style Language. Used for formatting XML documents.
<
A
B
C
D
E
F
G
H
I
J
L
M
N
O
P
R
S
T
U
V
W
X
Copyright 2007, 2023 Precisely