Training Run-through
Overview
[Describe what this topic is about. In Aria application documentation, include a link to the corresponding API documentation for the same feature, and vice versa.
Example: This article provides the steps for creating a plan.]
Important Notes
[Caveats/warnings to avoid unwanted consequences, if any. Scope of the feature (example: applicable payment methods). Rules that apply to the feature. If notes don’t apply to a feature overall, they can be included inline with the applicable step in the instructions.]
Best Practices
[Tips and tricks/best practices/recommended actions to achieve the best results, if any.
Example: Please see Plans Best Practices.]
Prerequisites
[Required actions or configuration setup needed before the feature can be used, if any.
Example: It is recommended that you complete the following minimum tasks before you begin to create plans:
- Create a service.
- Create a usage type (if applicable).]
Use Cases
[For detailed use cases, list the use cases, list the use cases that are documented and provide links to them. The use cases should include 3-7 examples showing common ways to use the feature. Use case documentation may include detailed steps for implementing each use case or at least the summary information listed below:
- Prerequisites/preconditions, if any. Example: Please see the Preconditions section.
- Required Steps. Example: Create an account with a future plan activation date and an alternate bill day.
- Outputs/Results: Example: The account is created and a prorated invoice is generated on the future plan activation date. Then a full invoice is generated on the alternate bill day.]