Once you've annotated your products with integration information and saved your stack, click on the Stack Map icon (looks like an asterisk) to see a visual representation of your stack architecture.
NOTE: It's important to click on UPDATE each time you visit your Stack Map to ensure that any changes to your integrations are reflected in the Stack Map.
There are a number of additional viewing options for your stack map:
Note:
You have the option to select Planned Integration and Related To in the integration drop down menu on Stack Annotations.
You also have the option of selecting Future Integration (represented as a dashed blue line), Planned Disconnect (dashed black line), or Disconnected/Inactive (dashed red line).
NOTE: Stack Maps and their associated integration notes can be exported as pdfs
If you are working to consolidate stacks across your organization or integrate an acquired company, creating a stack template can facilitate the process by creating a common language for your stacks.
Any stack can be used to create a template. Clicking on the Stack Template icon at the top of the stack will create a template that replicates your stack layer names. Templates can be shared with an individual, team or the entire enterprise. Templates do not show the products resident in the originating stacks.
If you have multiple organizations that are managing their own stacks, you can easily uncover duplicate contracts, products and functionality by creating a stack report.
Under Stacks in the left hand navigation click on Stack Reports and then Create a Stack Report.
Give your report a title and then select the report criteria including the stacks and stack fields that you'd like to include in your report.
When you click on Create Report, the system will produce a report consolidating stack information across the stacks you've identified by stack layer. Within the report you can move information columns around to create the report format you want.
Once created you can share any stack report with a specific team or the entire account membership. You can also download the stack report to share with other members of your organization.
Standard custom fields are creating within stack annotations and once created are applied to every product in one particular stack.
To create custom fields that are applied to every stack you create, click on Shared Annotations in the Enterprise Admin navigation. Custom fields created under shared annotations will appear with an S next to their label in stacks. These custom fields cannot be edited or deleted from within a stack, they must be edited or deleted within Shared Annotations. Users can however enter data into these custom fields within a stack.
With standard annotations, once annotations are added to a product in a stack, they will be displayed for every instance of that product in the stack in which they were created. If you add the same product to another stack, no annotations will be displayed even if they have been added in another stack.
There are two options to create annotation details that "travel" with a product from stack to stack.
1. Click on Shared Annotations and create an annotation record for a product. In this case, every time the product is added to a stack the user will have the option of choosing to use the shared annotation (by clicking shared annotation in the upper right of the annotation detail page) or to create a unique annotation for that product in the stack layer
CabinetM aggregates and anonymizes the data you provide about the products you are using and makes that information available under Stack Insights.
With Stack Insights you can see the top products in each category from the stacks being managed on the CabinetM platform. You can also look at the most popular products that surround the key platforms that you use.
Archive any Skill or Company stacks that you don't regularly use and that you might want to reference at a later day by selecting ARCHIVE when you delete a stack. Archived stacks can be restored at any time, included in Stack Filters and Stack Reports. Use Archived Stacks to compare Stack evolution year to year.
