| Top of Proposals | Index | Table of Contents | Feedback | |
This page enables users to view, record or edit details for a Proposal Instance they can also add new sections and remove existing sections.
The following users may edit a proposal:
Persons who are not editors, reviewers, proposers or administrators for a proposal will not be able to access that proposal in PAAW1100.
The shaded context panel in this page contains the details for this proposal, including:
The sequence of Sections and Items displayed on this page are determined for a proposal instance by its Proposal Type. Proposal Types are defined in PAAW0200.
In creating a Proposal Instance, the Selection Option chosen in PAAW1000 determines the Proposal Type for the proposal instance.
The user can record values or make selections for items defined for each section.
The ability for a user to view and or edit a proposal instance item may also depend on the restrictions defined for its element in PAAW0200 and by the current state of the proposal instance. Insert, Update and Delete restrictions for an element generally operate in a straight forward manner however the Insert Allowed, Update Not Allowed combination is further described below:
For a multi-instance element, any element item defined in the proposal type as 'Insert Allowed, Update Not Allowed' behaves as described in the table below.
| Proposal Based On | Element | Item Value | Item can be Edited? |
| Existing Curriculum item | Existing | NULL | Yes, Insert allowed |
| Existing Curriculum item | Existing | Non NULL | No, Update not allowed |
| Existing Curriculum item | New | N/A | Yes |
| Existing Proposal Instance | Existing | NULL | Yes, Insert Allowed |
| Existing Proposal Instance | Existing | Non NULL | No, Update not allowed |
| Existing Proposal Instance | New | N/A | Yes |
| Blank | Existing New |
NULL Not NULL Default value |
Yes, Insert allowed |
All items listed as Mandatory must contain values before the proposal can be submitted.
Note: On each page displaying the item fields in an section, clicking any of the buttons will result in the current record being saved.( This includes tool bar buttons such as the Print and Email buttons). The Close Proposal link does not save the record directly, it gives the user the option to save the record or not before returning to PAAW1000.
On this page the user can click on a tool bar button at the top of the screen to:
The sequence of Proposal Sections and Items appearing in PAAW1100 is determined by the structure of the Proposal Type for the proposal instance.
This sequence may also depend on the current stage of proposal development and the 'Display When' values defined in PAAW0200. e.g. If an element has has a 'Display When' setting of '- Is displayed for entry once the proposal is submitted for review', then it will not be included in the sequence of sections displayed in PAAW1100 before submissions.
This sequence of sections may also be affected by 'Display When' conditions defined in PAAW0200. e.g. A Proposal Type is defined such that a Course Item is not displayed when the Course Type is not '10'. In this case, the item will not appear for any proposal instance where the course Type is not '10'.
Note that 'Display When' conditions defined in PAAW0200 allow for a specific instance of an element or item to be visible. e.g. A Proposal Type is defined such that Unit Offering Option G is only be displayed when the Unit Offering = SEM-1. In this case this option will not be displayed when a reviewer is examining Unit Offerings other than SEM-1.
Note: If the value for an item in a proposal instance is updated such that it causes another item to be displayed/hidden then that will occur in real time and have an immediate effect on the sections displayed.
Note: Proposal Items that have been closed in PAAW0300 will not be included in PAAW1100 unless an instance of the item was created in this proposal instance before the item was closed.
Some elements consist of multiple sets of items e.g. Multiple teaching responsibility records for a unit. These are created separately in PAAW1100 but each instance of the element is displayed as a row in a summary table.
Up to 10 multi-instance item records can be listed in the summary table, with other records accessible via the scroll bar.
When the user updates the details of an item instance and returns to the summary table, they are returned to the last updated record on the list.
If the 'Display Summary Total' check box is selected for the item in PAAW0200 then the sum of the item instance values is also displayed.
In the summary table:
Click on the New icon to add a new instance of the element.
Click on the Remove icon to remove the selected instance(s).
Click on the Reinstate to
cause the return of an element instance that was just removed. (Note that if this was newly added and not part of the original curriculum on which this proposal is based, then it cannot be reinstated).
Click on the Export to Excel button to export the contents of the summary table to an Excel spreadsheet.
In addition to standard editing privileges (via roles and conditional statements), if the proposal is updating an existing curriculum item, the ability of a user to update existing instances of an multi-instance element can be controlled by the 'Allow Update' check box for the Element in the Proposal Type as defined in PAAW0200. Likewise if the 'Allow Delete' check box is not selected for the element in PAAW0200 then existing element instances in an update proposal cannot be deleted, and if the 'Allow Insert' check box is not selected then new instances of the element cannot be added.
The order of the rows in the table is determined by the Summary Order values recorded for each element proposal item in PAAW0200.
This sort order can be modified here by clicking on a sort icon in the column heading that you wish to sort by. If this occurs a new Default Sort icon becomes available to allow the restoration of the sort order defined in PAAW0200.
Note that summary table default sort (from PAAW0200) displays a a blank value after populated values in ASC sort order, whereas when the summary table is sorted manually (via sort icon in PAAW1100) then a blank value comes before populated values in ASC sort order.
Also, when a summary table is sorted manually for a proposal instance, secondary sorting will occur according to the default sort order.
Sections in a proposal instance may require complete records to be entered. Such proposal instances cannot be submitted unless these mandatory sections are completed. Likewise Individual Items in a proposal instance may require an entry to be recorded.
The mandatory requirement of these Sections or Items is defined for the Proposal Type for the Proposal Instance. Proposal Types are defined in PAAW0200.
Mandatory Requirements may also be affected by 'Mandatory When' settings for Elements and Items in PAAW0200.These can be set so that Elements or Items in a proposal may only be mandatory at certain times during the development of a proposal. Conditional statements may also be recorded for an element or item such that it will only be mandatory when certain conditions are satisfied, for example, a Course Item may only be mandatory when the proposal instance has a Course Type = '10'.
lamp displayed alongside an element indicates that all Mandatory Items contain an entry.
lamp indicates otherwise.You can create a new Proposal based on an existing Proposal or based on an existing curriculum item in the Course Structure and Planning (CRS) subsystem. If you base the Proposal on an existing curriculum item, the curriculum item and associated data is automatically transferred from the CRS subsystem into the Proposals (PAA) subsystem for the new Proposal. The Proposal Instance Proposal Type determines which tables are selected in the CRS subsystem. (Data is displayed in PAAW1100.)
The Edit Rules page is displayed for elements that map to a System Type of UVRULE or USRULE.
Units:
The following types of rules can be created for units:
These rule types are described in Unit Version Rules.
Unit Sets:
The following types of rules can be created for unit sets:
These rule types are described in Unit Set Rules.
For each rule required, enter a description of the rule and then click on the associated Rule button to open RULW2000.
Note: Course Rules are not currently available.
To include Structures (CRSW2600), Dependencies (CRSW2600) and Timelines (CRSW2650) for a Proposal Instance, the Proposal Type (PAAW0200) on which the Proposal is based must include a Structure Element mapped to the relevant System Element Code: for Course Proposals the System Element is CRVS, for Unit Set Proposals the System Element is USSTRU, for Unit Proposals, UVSTRU.
The Structure, Dependencies and Timeline pages are accessed from the Structure Element step of the Proposal Instance (PAAW1100) page, as follows:
When you first access the Structure/Dependencies page (CRSW2600) in the Proposal Instance (PAAW1100):
When the Proposal is approved and transferred by the relevant Transfer job into the CRS subsystem, its Structure, Dependencies (and Timelines, if relevant) are included in the transfer; only if at least one of them has been modified. The transferred Structure and Dependencies replace the existing Structure and Dependencies instances in the CRS subsystem for the context curriculum item, and become the 'latest instance'. The previous instances are automatically end-dated and are no longer viewable. For more information, see Structures and Dependencies in Proposals.
Custom validations can be configured for Proposal Items in PAAW0300. These validations can be triggered by changing the focus of the cursor or tabbing off into a new item, or by changing or saving the item value. The message output is of the form: '<Error/Warning/Info> Message returned from client validation: <return message>' and will operate the same as Callista's built in messages.
Return to Top
Default item values can be defined for Proposal Items in PAAW0300. Default values can be actual values or values derived by an SQL statement. If the system cannot determine the default value using the SQL statement, then the default value will be null.
To include Outcome Frameworks (CRSW3000) for a Course Proposal Instance, the Proposal Type (PAAW0200) on which the Proposal is based must include an Element mapped to the System Element Code CRSOUTFW.
At the step where Outcome Frameworks are to be updated or created for a Course Proposal:
f the proposal is updatable and has an existing framework, the Outcome Framework button is displayed which will launch CRSW3000 this Course Proposal in context and the current framework displayed.
If no framework exists, then the No Outcome Framework Associated to Proposal button is displayed, which will launch CRSW3000 with a new, empty framework .
When the Save & Close or Cancel button in CRSW3000 is clicked, the user is returned to PAAW1100 to proceed with the next step in the Proposal.
Page last modified: 21 November, 2016 3:23 PM
History Information:
| Release Version | Project | Change to Document |
| 19.0.0.2 | 2234 - PC318 | Added Custom Validations and Default Item Values sections. |
| 19.0 | 2106 - Course Outcomes | Added section about Course Outcome Frameworks |
| 18.1 | 2174 - PC351 | Added note about Insert Allowed, Update Not Allowed combination |
| 18.0 | 2074 - Proposals Functional Updates | Added note about navigation and display for multi-instance items. |
| 17.0.0.2 & 17.1 | 2000 - PC307 | Added note about Closed items not appearing in this page. |
| 16.1.0.2,17.0 | 2003 - CAPS 2014 | Added Multi Instance Elements section |
| 17.0 | 1955 - Course Structures in Proposals | Added a new section: Course Structures & Dependencies. |
| 16.1 | 1820 - Phase 3 | Added info to step 7 in the 'Creating a Proposal Based on Existing' instructions. |
| 16.0 | 1844 - CAPS enhancements | Added administrators as being able to edit proposals. Added new sections on Sequence of Elements and Items and Mandatory Elements and Items. |
| 15.0 | 1722 - 11g Upgrade | New Help page for 11g. |