Scenarios → Simple Scenario #1

Simple Scenario #1

This is the overview for a simple scenario. It should be consise, to-the-point, and maybe not more than two paragraphs (or one paragraph plus workflow diagram). The following tasks are just placeholders used to represent the actual steps in a simple scenario (one to six steps, no more).

Use the information in the following topics (moving from left to right) to complete this scenario.

Step One

This is the short introduction to the steps to be followed in step one. If the user needs to enter a specific value, note that in this introduction. For example, "Use the following steps to create a custom attribute. Be sure to enable the Value, Option, and Closed options." (or something to that effect).

To ... (step one)

  1. From the top-level navigation, open the Admin module.
  2. Select System Settings.
  3. Select the Scheduled Services tab.
  4. Select the Jobs tab.
  5. Select a job.
  6. Under Scheduled Job Properties, define the schedule that this job should run. Jobs should be scheduled during time of the day where users are not logged onto the system. In most cases, running of a scheduled job will log off users or cause interruption to their use of the system.
  7. Click Save Save.

Step Two

This is the short introduction to the steps to be followed in step two. If the user needs to enter a specific value, note that in this introduction. For example, "Use the following steps to create a custom attribute. Be sure to enable the Value, Option, and Closed options." (or something to that effect).

To ... (step two)

  1. From the top-level navigation, open the Admin module.
  2. Select System Settings.
  3. Select the Scheduled Services tab.
  4. Select the Jobs tab.
  5. Under Status, click View Job History.

Step Three

This is the short introduction to the steps to be followed in step three. In some cases, it may be necessary for a "step" to be just content, without actual steps. In this case, this information would still live within the tabbed structure, but would just contain content and no steps. Like this.

Step Four

This is the short introduction to the steps to be followed in step four. If the user needs to enter a specific value, note that in this introduction. For example, "Use the following steps to create a custom attribute. Be sure to enable the Value, Option, and Closed options." (or something to that effect).

To ... (step four)

  1. From the top-level navigation, open the Admin module.
  2. Select Customization.
  3. Select the Attributes Setup tab.
  4. Select the Attributes tab.
  5. Click New New.
  6. Name the new attribute. The system name will be generated automatically.
  7. From the Type drop-down, select milestone.
  8. From the Rollup Type drop-down, select none (default, no roll-up), min (selects the lowest value or earliest date from an attribute's direct descendent values), or max (selects the highest value or latest date from an attribute's direct descendent values). An attribute with a rollup type other than none will be saved as a global attribute.
  9. Select Global to make the attribute a global attribute. A global attribute is required for all item types and optional for all work types.
  10. Select Searchable to allow users to search for the attribute in the Projects and Reports modules.
  11. Milestone attributes are always part of an attribute list. Under List Attributes, choose an attribute list to which the milestone attribute will be associated. Milestone attributes are always dimensioned, but they cannot use MathML calculations.
  12. Click Save Save.

Step Five

This is the short introduction to the steps to be followed in step five. If the user needs to enter a specific value, note that in this introduction. For example, "Use the following steps to create a custom attribute. Be sure to enable the Value, Option, and Closed options." (or something to that effect).

To ... (step five)

  1. Open the Projects module.
  2. Select an item.
  3. Select the Risks tab.
  4. Select a risk.
  5. Make your changes.
  6. Click Save Save.

Step Six

This is the short introduction to the steps to be followed in step six. If the user needs to enter a specific value, note that in this introduction. For example, "Use the following steps to create a custom attribute. Be sure to enable the Value, Option, and Closed options." (or something to that effect).

To ... (step six)

  1. From the top-level navigation, open the Admin module.
  2. Select Manage Users.
  3. Select the Security tab.
  4. Select the Users tab.
  5. Click New New.
  6. Under User Properties, enter the first and last name for the user, their user name and their email address.
  7. Leave the Distinguished Name field empty. If your organization is using a directory service to create user accounts, such as Microsoft Active Directory or Novell eDirectory, this field will contain the user's Lightweight Directory Access (LDAP) distinguished name. For example: cn=grant mclennan,ou=australia,dc=gobetweens,dc=com.
  8. From the Authentication Provider drop-down, select the provider that will be used when this user logs on. In Password, type the password for the user. Passwords are case-sensitive and must be at least four characters long; blank passwords are not allowed. You do not need to enter a password if your organization is using a directory service.
  9. Select Active to make this user available; only active users can access the application and/or be available for selection.
  10. Select Send Email Notifications to allow the user to receive notifications by email.
  11. Under Global/Administrative Roles, select the security roles to which you want to assign this user.
  12. Under Licenses, select the licenses to which this user is assigned. All users must have a license assigned to them.
  13. Click Save Save.

Copyright © 2003–2009 Serena Software, Inc. All rights reserved.