Additional Export and Import Actions
The following export and import actions are available, but are not presented as options in the graphical user interface.
Additional Lock Export Action
The lock action can be imposed through an import policy file or the system registry.
Additional Import Actions
The following actions can be imposed through an import policy file or the system registry:
• Use UnlockAndIterate to find an object in the database with the same UFID or the same name, number, version, and iteration as the object in the XML file. If a match is found and it is locked, this action unlocks and iterates it, and then updates it with information from the XML file. Otherwise, the action generates an error.
• Add new attributes based on what you would like added to the configuration as well as the user’s preferred setting. This not only makes the installation process easier, but also makes the process much easier to track when you upload your data to the load cache server.
• Use CreateNewObject to create a new object with the new name, new number, new version, and new iteration provided in the import policy file. Other information is extracted from the XML file. This functionality must be used with a policy file that provides new identities for the object.
The format for the new information that must be provided in the import policy file is the following:
Please note that:
◦ <actionInfo> must always exist.
◦ Criteria can be any valid attribute of the object in XML file.
◦ Between the <xsl:choose> tags, there can be many <xsl: when test ....> tags with different criteria and different action names.
◦ Only CreateNewObject and SubstituteObject can have action parameters, and there are only four action parameters: <newName>, <newNumber>, <newVersion>, and <newIteration>. All four parameters must be provided.
• Use SubstituteObject to substitute the object in the XML file for an object in the database that has the name, number, version, and iteration provided in the import policy file. If a match does not exist, it generates an exception. The format of the tag and parameters is exactly the same as CreateNewObject, but the <action> is SubstituteObject.
• Use Ignore to prevent the object in the XML file from being imported. This action does not require any actor.