Adaptive CLI FAQs
• Why share an existing schema from another Adaptive CLI (ACLI) versus creating a newone with each ACLI?
One reason to use the same schema is to accommodate a complementary ACLIs. For example one ACLI creates an entity and you want a script to remove the same entity. For such examples, the valid values, labels, and so on, for the attributes are always going to be the same in your create and delete ACLIs. Therefore, it is safe to use the same single referenced version of the Schema. You can share the same schema, and your delete script can mark the attributes it does not use as Not applicable.
• What is the best practice for exporting ACLIs to import later into another system?
If you have ACLIs that you need to export so that you can import them into another Redcell installation, then the recommended practice is to create a separate file for each ACLI and export them one at a time.
You can group select multiple ACLIs in the Adaptive CLI Manager and export them to a single file, but this can be difficult to maintain if changes are being made frequently to the ACLIs. Best practice is that only ACLIs directly sharing a common Schema (example a Create ACLI and its complimentary Delete ACLI) be exported to the same file. Keep in mind how to maintain/version/update the ACLIs and associated shared schemas when plotting how to map your export files, and frequently back up your export files to external devices/machines. You can use source control systems version/maintain ACLI export files, since they are in XML format.
• If I change an ACLI’s schema shared by other ACLIs, do I need to do anything to the other ACLIs?
If you have multiple ACLIs sharing the same Schema, you should be in the habit of retesting the other ACLIs using that schema for to ensure no unintended side effects occur.
Regularly export all ACLIs with the same schema before modifying the schema by editing any of the ACLIs that use it.