Best Practices

Review these best practices for setting up and configuring your Fusion Manage site.

Permissions

• Create two permission roles for each workspace to separate read-write functionality permissions from read-only functionality permissions. Name the roles Workspace Name [R/W] and Workspace Name [R] .
• Create a role for each use case in a workspace to separate out workflow functionality. Names these roles based on the function or intent within the workflow, for example RFQ [Supplier].
• Assign all permissions to the Admin user account to avoid unwanted user accounts. Create and Admin permission group and associate it with all workspace [R/W] and [WF] roles. Add the Admin user to the Admin group.
• To enable safe editing of latest releases and superseded revisions of revision-controlled items, first create a special permission role (for example, Override Revision Control Locks Role) and add the Override Revision Control Locks permission to the role. Then create a special user group (for example, Override Revision Control Locks Group) and associate the role with this user group. Finally, add the appropriate users to Override Revision Control Locks Group. With this setup, only users added to this special group have permission to edit latest releases and superseded revisions of revision-controlled items.

For help on setting up roles, groups, and users, see Set up Permissions.

Fields

• Configure an Autonumber field for each workspace (Revision-Controlled Workspaces excepted). Call the field Number and configure it to start with a two-letter code for the workspace, followed by a six-digit sequence, for example CR000001.

• Prefix workspace Picklist fields with [WS].

• Standardize field lengths.

  Field Type	Length	Display Width	Precision	Maximum Length
  Numeric	25	25	3	n/a
  Single Line Text	50	50	n/a	n/a
  Paragraph	n/a	50	n/a	512
  List	n/a	50	n/a	n/a
  Grid	50	25	n/a	n/a

For help on configuring workspace fields, see Configure Forms and Views.

Workflow

• Prefix workflow state names with a sequence indicator, starting with [01].
• Do not use numbers in workflow transition names.
• Prefix workflow permission names with the two-letter code used in the workspace Autonumber field.
• Be sure to apply locks to workflow sections as needed. Locking is off by default.

For help on creating workflows, see the Workflow Management.

Scripting

• Prefix script names with a logical workspace identifier.
• Prepend a standard prefix to names of frequently used scripts, for example Gen.
• Use an “introductory” programming style to make code easy to read. Avoid using complex techniques unless absolutely necessary.
• Comment your code extensively.

For help on writing scripts, see Developer's Scripting Guide.