Managing Transaction Sets

every time you add, delete, or modify the configuration, the application records the changes these recorded changes are called a transaction set for example, every time that you save changes for a business object, the application records the changes in a transaction set the application tracks every change and assigns each change a sequential number creating a transaction set follow these steps, to create a transaction set from the configuration console, click build > development project > projects to display the projects workspace the application displays a list of all the projects from the project drop down menu in the toolbar, select the project to which the changes you are going to make will belong make changes to as normal for example, you can create a new business object, form, or list in certain cases, when you make changes to neurons for itsm, you must enter your user name and password when you create and later export the transaction set as part of a package, the package file exposes the user name and password to avoid exposing this potentially sensitive information, we recommend that when setting the user name and password for an integration connection, instead of entering a value, you use a global constant see using global constants to hide login id and password information docid\ mirdh rhcg0jei2i56fmm for information see viewing, editing, cloning, and deleting incoming web service connections docid\ j7tnsjafp3ohqrnokepmv for an example of using a global constant in this situation if you do not use a global constant for the user name and password, the application removes that information from the transaction set viewing transaction sets from the transaction sets page, you can view the relevant changes that are linked to a transaction set you can search by transaction set id use the transaction set id when creating a package from the configuration console, click build > development project > transaction sets to open the transaction sets workspace the application displays a list of all the transaction sets the application displays the following information field description id the id for this transaction set created on the date when the transaction set was created user id the id of the user who created the transaction set session id the id of the session when the transaction set was created db revision the database revision source specifies where the transaction was made adminui means that the change was made in the configuration console, and a tenant url means that the change was made from a package migration project name the name of the development project to which this transaction set is attached double click a transaction set and click the transaction detail tab to see the following information field description project name the name of the development project to which this transaction set is attached transaction set id a sequential number linked to the change a transaction set may contain zero or more changes (a zero change indicates the change was aborted, and was not recorded ) detail id a sequential number linked to the change a detail may contain zero or more changes (a zero change indicates the change was aborted, and was not recorded ) user id the id of the user who created the transaction set operation date time the date and time when the change was recorded operation type the type of operation can be c for new record, u for modification, or d for deleted object type the type for which the change applies the values can be businessobject for a business object change, form for a form change, or a business object name such as accountstatus# for change in its data, etc business object the name of the business object to which the change is linked, if any entity name the key for the business object record itself in some cases, it is the guid and in other case, it is a name, such as a business object name, a form name, or a role name source id the key for the business object record itself in some cases, it is the guid and in other case, it is a name, such as a business object name, a form name, or a role name to publish specifies if this transaction set can be published y the change is packaged n this change is a side effect of another change that is published