Top of Proposals

Index

Table of Contents

Feedback

Proposals Set Up

Table of Contents

• Security
• Calendars and Dates
• Communications
• Workflow
• Proposals

Security

1. SECF0061 - Maintain Menus and Menu Items
   Build Menus, sub-menus. Include forms, jobs and web pages in menu structure.
2. SECF0063 Maintain Security Role Function Grants
   Enable access by people with particular security roles to the required menus, forms, jobs and web pages
   Allocate Advanced Functions to particular security roles.
3. SECF0062 - Maintain Person Function Grants
   Enable particular users to access the required menus, forms, jobs and web pages
   Allocate Advanced Functions to particular users.
4. SECF0065 - Maintain Proposal Type Restrictions (via SECF0063)
   Restrict the type of proposals that people with a particular security role can create.
   (Proposal Types are defined in PAAW0200. See below.)

Calendars and Dates

1. CALF0410 - Maintain Date Alias Categories
   Define a Date Alias Category of PROPOSALS, to make it available for selection when creating date aliases in CALF0420.
2. CALF0420 - Maintain Date Aliases
   Define date aliases to provide start or end dates for Proposal activities.
   
3. CALF0511 - Create Date Alias instances
   Create instances of these Date Aliases in the appropriate Calendar Instances.

Communications

1. CORW0400 - Substitution Tags
   - Define local names for System Email Substitution Tags.
   - These will return specific database values when the tags are embedded in Email types in CORF2660 and thus pick up value when the message is created.
2. CORF2660 - Maintain Email Type
   - Email Types define the content of email messages. e.g. To notify proposer that a proposal has been transferred.
   - These may be selected for Issue for various events during the proposal process.
   - May also be selected as part of a Communication Type Group in CORW2690.
3. CORW2690 - Communication Template Groups
   - Create Template Groups if you wish to define sets of Email messages that will be delivered together in a single email.
4. GENF0100 - Maintain Document Type
   - This form allows document types (with a System Document Type of PROPOSAL) to be defined. These will then be available to associate with elements in a proposal.
   e.g. An element of Library Resources may define items to collect the details of all books that are required for the unit. Against this data, the proposer may be required to upload a library justification document to explain how the books will be utilised in the unit. This document can be defined as a Document Type and then associated to the element to inform the proposer that they must upload this document.
5. CORW0100 - Communication Source
   - Use this page to define which Callista email address is used as the email address to which email communications are addressed
   - Different Callista email address sources may be specified for communications with different Priorities.
6. GENW0040 - Style Class
   - Name and describe styles so that these values are available in GENF4820. The styles class names should give meaning to style classes set up by technical developers for display in callista pages.
7. SSFF5000 - Maintain Self Serve Notice
   - Define Proposal Notices that will display to Proposals users.

Workflow

See Workflow in Proposals.

1. GENF4880 - Maintain Workflow Instance Step Status
   - Define local workflow step statuses and map them to system status values.
   - The status describes the current state of the Workflow Step.
   - System statuses are PENDING, IN PROGRESS, COMPLETED, FAILED, REQUEST INFO.
2. GENF4900 - Maintain Business Activity Processes
   - Name BAPs and map them to System BAP codes.
   - These BAPs will be allocated to Workflow Steps.
   - BAP values defined here will be available in GENF4920 - accessed in context of an org unit, course version, etc.(see below)
3. GENF4920 - Maintain Business Activity Process Member
   - Accessed via context form e.g. ORGF0141 for org unit BAPs
   - Select BAP(s) relevant for this context and allocate staff to them.
   - Select the Active BAP members. These are the decision makers when the BAP is used in a Workflow Step.
   
4. GENF4910 - Business Activity Process Person
   - BAPS of type USER-PE are defined in GENF4900. but their membership does not have a common context, so the members are listed separately here.
   e.g.An Institution's Ethics committee, Deans
   - The BAP members defined as Active are the decision makers when the BAP is involved in a Workflow Step.
   
5. GENF4820 - Maintain Workflow Step
   - Create the Workflow Steps that will be included in Workflows (in GENF4830).
   - Record a BAP for each Workflow Step (will determine the people to perform the step).
   - The step order defines the sequence of the workflow steps.
   - Record Review Date Aliases or the Review Days to define when the Workflow Step should be completed. If the Review Date Alias is recorded, the system looks for the next instance of the date alias after the workflow step is initiated. If a Review Days value is recorded it is due on that number of days after the workflow step is initiated.
   - When the workflow step is initiated, the members of the BAP should be notified via a Email (from CORF2660) and/or the Notice (from SSFF5000).
   - The appearance of the messages to appear for BAP members in PAAW1000 can also be defined here. The colour and style of the text is determined by the Style Class selected (These style classes are named in GENW0040). The timing of the display is determined by the Days and Timing values recorded.
   - All active members of the BAP for a Workflow Step must respond before a workflow can continue.
6. GENF4830 - Maintain Workflow
   - Use this form to list workflow steps for a workflow.
   - Once Workflow Steps are defined in GENF4820 they can be allocated to Workflow in this form.
   - These will be listed in order when a workflow is included in a Review Category. (See below).
7. PAAW0500 - Review Categories
   - Use this page to create Review Categories and associate Workflows with them.
   - Review Categories are assigned to Proposal Types in PAAW0200, or can be derived according to Proposal Outcomes and Amendment values.
   - Record what to do when a workflow step fails.
   - Record who to contact when a workflow step fails and what to say

Proposals

1. PAAW0100 - Proposals Configuration
   - Configure various deadlines and default settings for Proposals on this page. e.g. Communication methods, types, frequency
2. PAAW0130 - Proposal Transfer Statuses
   - Use this page to give local names for System Transfer Statuses.
   - Map to CANCELLED, COMPLETE, READY, NOT-APPLIC, PENDING, TRANSFER ERROR
   
3. PAAW0300 - Proposal Items
   - Use this page to create Proposal Items which correspond to Callista Course Structure and Planning system items.
   - Set up how a person creating a proposal will see the item when they are creating a proposal in PAAW1100.
   - You can also can create your own data items and map them to user-defined system items which are not transferred to the Course Structure and Planning tables.
4. PAAW0200 - Proposal Types
   - Use this page to define Proposal Types - These are made up of elements which include items (defined in PAAW0300 above).
   e.g. An element called Basic Unit Details may have items such as Unit Name, Unit Code, etc.
   - Sub-elements may also be defined to an element, implying a structure. Within each element the user can create relationships to other elements. This allows the linkage of elements to identify dependent or related elements.
   e.g. Unit offering options and unit offering patterns - a relationship would need to be defined between the elements.
   - Items and sub-elements may be related to each Proposal Element.
   - All of this structure and information builds a menu in the PAA1100 and and defines the data displayed on each page.
   - One Proposal Type is selected as the 'Definitive Instance' for each System Proposal Type. This is typically the complete set of data required for a Unit, Unit Set or Course.
   - The Selection Option recorded for the Proposal Type defines the link that the Proposer selects to create a proposal of this Proposal Type.
   - The Proposal Type should also have Review Category(s) defined to determine the review workflow for this Proposal Type.
5. SECW0066 - My Proposal Preferences
   Each user should record their personal preferences of this page. This includes:
   - Recording the editors for your proposals.
   - Nominating how you wish to receive your Proposal messages (email, notice or both) and on which day(s).
   - Selecting what proposals you wish to subscribe to.

Return to Top

Page last modified: 31 May, 2012 4:23 PM

History Information: