Overview
A Change Request is a business object representing a proposal by a User to change the existing structure. It can be a correction, enhancement or even a deletion of something that is identified by the requestor as wrong. It can also consist in new additions of various Structure elements.
Change Requests usually undergo an approval workflow before they are released.
Following their release, no structure element is deleted. Structure elements can be withdrawn, as well as various elements can be assigned. But all structure elements will remain part of the dictionary and simply be marked as deprecated. This means that they are kept in the database and can be reactivated in a future release if needed.
Further details on the graphical user interface are here.
/*<![CDATA[*/ div.rbtoc1770892094433 {padding: 0px;} div.rbtoc1770892094433 ul {list-style: disc;margin-left: 0px;} div.rbtoc1770892094433 li {margin-left: 0px;padding-left: 0px;} /*]]>*/ Overview General Information Toolbar Search Options Details Collect Submit Archive Delete Export Import Eptos XML Import Excel Version 6.0 Import
General Information
The workspace area for the management of own Change Requests can be accessed via menu My change request. Here, various actions in connection to them can be performed (e.g. edit, submit, delete, export etc.), except create them. This can be done under the specific menus in Classification Manager, corresponding to the Structure element type for which a Change request is needed.
Thus, this area offers users different functionalities described in brief in the following table as well as in more detail in the next chapters.
Toolbar
|
Button Icon |
Button Name |
Description |
|---|---|---|
|
|
Search |
Triggers a search in the available content, considering the search options set in the advanced search. |
|
|
Collect |
Allows the collection of Change Requests in a list from where further actions can be taken and applied to all. |
|
|
Submit |
Allows the submittal of desired Change Request(s). |
|
|
Archive |
Allows the archiving of desired Change Request(s) |
|
|
Delete |
Allows the deletion of selected Change Request(s). |
|
|
Export |
Allows the export of desired Change Request(s). |
|
|
Import |
Allows the import of desired Change Request(s). |
|
|
Start Workflow |
Allows starting a workflow for selected Change Request. |
|
|
Remove |
Allows users to remove the selected entries from the list of collected Change Requests. |
|
|
Remove all |
Allows users to remove all entries from the list of collected Change Requests. |
Search Options
There are several search options available in the system. Some of them are structured as comboboxes, in which all possible values are predefined, others allow entering of free text.
These options can be used individually or combined.
|
Option |
Description |
|---|---|
|
Status |
Allows searching by Change Request status. Combo-box contains all statuses available in the system: Accepted, Closed, Confirmed for accept, Draft, New, Next release, Proposed for accept, Proposed for reject, Proposed for rework, Received, Rejected, Rework, Submitted, Translated. |
|
Type |
Allows searching by Change Request type. Combo-box contains all types available in the system: Assign, Change order, Change textual info, Copy, Enable value, Join, Merge, Move, New, Reactivate, Remove, Replace, Split, Withdraw. |
|
Entity type |
Allows detailing the search by Change Request type by Entity type as well: e.g. User selects "New" in box "Type" and "Classification Class" in box "Entity type". System returns all results of type "New Classification Class". |
|
Creation date - from |
Allows entering the precise date and time starting from which the search should be performed. Value format is prefilled, user just needs to modify the numbers accordingly. |
|
Creation date - to |
Allows entering the precise date and time until which the search should be performed. Value format is prefilled, user just needs to modify the numbers accordingly. |
|
Text |
Allows entering Change Request ID, Change Request Name or parts of them. |
|
Property data type |
Allows searching by specific data types in the case of Property related Change Requests. |
|
Source release |
Allows selection of specific source releases in which the search after Change Requests should be performed. |
Details
In order to view more details related to a Change Request, users may open the Change Request by clicking on it from the list view.
The details page of a Change Request is subdivided into different tabs. The visibility and order of the displayed tabs is configurable by users with configuration rights. Furthermore, custom tabs can be created.
Tabs which do not contain any information are grayed out.
The following table gives an overview of the tabs available for Change Requests:
|
Tab Name |
Description |
|---|---|
|
General |
Tab General displays the standard attributes of a Change Request. The visibility and order of the attributes displayed in tab General is configurable by users with configuration rights via the Validation Framework. |
|
History |
Tab History displays historical information on the selected Change Request, meaning the exact date and time of each status change, starting with its creation until its closing, as well as the assignee corresponding to each change. |
|
Change requests |
Tab Change requests displays all Change Requests referencing selected Change Request |
|
Change requests composing the operation |
Tab Change requests composing the operation displays all Change Requests contained by the selected Change Request e.g. in the case of a Split Classification Class Change Request, the tab will include Assign Property to Application class Change Request(s) (referring to the classes where the Property was assigned to via the Split operation), Assign Aspect to Application class Change Request(s), Assign keyword to classification class Change Request(s) (if the Class being split had Keywords), Remove Classification Class Change Request (referring to the Source Classification Class of the split operation), Remove Application Class Change Request (referring to the Source Application Class of the split operation). |
Collect
This functionality allows users to collect Change Requests in view of further operations which should be done in bulk to the selection (submit, delete etc.)
Change Requests can be removed from the collection by using buttons Remove (for selected Change Requests) or Remove all (for removal of entire collection).
Submit
This functionality allows users to submit Change Requests for review. The recipient User/Group receiving these Change Requests depends on the individual system settings.
As soon as Change Requests in status New are selected and button Submit is pressed, system will automatically change respective Change Requests to status Received.
Change Requests referencing other Change Requests in statuses Closed, New, Rejected, Rework cannot be submitted. These must either be included in the submit operation or be submitted separately.
e.g. Change Request of type Assign Application Class to Classification Class cannot be submitted if it references for example a Change Request for New Classification Class in one of the statuses indicated above.
User either first submits the New Classification Class or submits it together with the Assign Change Request.
Archive
This functionality allows users to archive Change Requests which are no longer needed.
Change Requests in following statuses can be archived: Rejected, Rework, Accepted.
Once archived, system turns respective Change Requests to status Closed.
Delete
This functionality allows users to delete Change Requests which are no longer needed.
Change Requests in following statuses can be deleted: New, Draft.
Once deleted, system permanently removes respective Change Requests from the database.
Export
This functionality allows users to export Change Requests from the system.
Users may export all or a selection of Change Requests in one of the available export formats: XLSX or XML.
Following export options may be defined in the graphical user interface:
|
Option |
Description |
|---|---|
|
Export type |
The Export type option offers the following selection possibilities:
|
|
Export range |
The Export range option offers the following selection possibilities:
|
|
|
Allows users to input the e-mail address where the exported file will be sent. |
|
All languages |
Allows users to indicate via checkbox if all available languages should be included in export file. |
After desired options are selected and Export button is pressed, the operation will be started in the background. The exported file will be sent per e-mail to the specified e-mail address.
Import
This functionality allows users to import Change Requests into the system.
Users may import Change Requests in one of the following import formats: XML or XLSX. As a first step, he needs to press Import button in toolbar under My Change Requests list.
Eptos XML Import
Following import options may be defined in the graphical user interface:
|
Option |
Description |
|---|---|
|
Import type |
Eptos XML export |
|
Release |
Allows selection of the release into which Change Requests will be imported. |
|
Set current user as change request proposer |
Allows user to check this option if desired. |
|
Import file |
Allows browsing the XML import file from the computer. |
|
Check only |
Allows user to chose if import file should only be checked by the system, without the contained Change Requests being saved. |
|
|
Allows users to input the e-mail address where the import report will be sent. |
Excel Version 6.0 Import
As soon as User selects Excel Version 6.0 Import type and then presses Next button, system will open the XLSX import interface, containing following options:
|
Option |
Description |
|---|---|
|
Import file |
Allows browsing the XLSX import file from the computer. |
|
Import type |
Allows user to select one of the following options:
|
|
Release |
Allows selection of the release into which Change Requests will be imported. |
|
Import mode |
Allows user to select one of the options "Complete check" or "Save change requests". |
|
|
Allows users to input the e-mail address where the import report will be sent. |
|
Check only |
Allows user to chose if import file should only be checked by the system, without the contained Change Requests being saved. |
|
Show warnings in error report |
Allows user to check this option if desired. |