Publish to production
This information relates to the UniSAinfo Reporting development environment.
When the cube or report is ready to be made public, it must be published to the Production server (\\ituprod-bi1).
To do this, complete the Publication Form below using the instructions on this page as a guide.
The latest Publication Form (which is an excel document) can be downloaded by clicking here.
Then email to the completed form as detailed below.
1. NewsBox Item Name
This must match file name of the NewsBox item in \\itudev-bi1 that is to be
published. Your file name should not contain any reference to what type of
item it is. For example if your item is called Student Enrolment Cube delete
‘cube’. This distinction will be obvious when displayed in Upfront (via
icon). When this cell is filled out the name appears in the red title bar.
2.Type of NewsBox Item
Developers are to pick from the drop down list. When selected the object
type is displayed alongside the name in the red cell, see below
![]() |
Figure 1
3. Date Published
Enter current date.
4. Area
Select an area that the developer belongs to.
5. Contact/Author
Provide the name of the most appropriate person that users can contact for
issues relating to the NewsBox Item.
6. Please provide a summary about the information contained in the
NewsBox Item
Use this section to specify what type information the item will show. The
detail needs to be precise and not open to misinterpretation. Provide as
much detail as necessary to inform users of how the data is collected, and
any business rules inherent in the data that users should be aware of.
7. Who would find this Item useful (other than area that data comes from?)
Tick any of the generic values and/or if necessary add others.
8. Cohort Category
If the item is to be published in a specific cohort select the category from
the drop down list.
9. UniSA Public Category
If the item is for ‘public’ users select the category from the drop down
list.
10. UniSA Public Sub-Category
If your item is to reside in a sub-category of UniSA Public select the
sub-category from the drop down list.
11. Refresh Details
Provide details on when the most current data will be available in the
NewsBox item, more specifically please provide information re the frequency
of updating and the estimated date of an update eg. monthly on the 15th or
daily @5:30am.
12. Brief Description of NewsBox Item
This is a condensed version of the item’s full description as detailed in
part 6. . The length needs to be contained to 15 words as it will be
displayed when published. Some key words suitable for users to search on
should be a consideration.
13. Provide UniSA Restricted Details
If you development belongs to this category, provide details of the
sensitivity of the data.
Manager will need this information to decide if other ‘public’ users will be
given access to the information.
14. Provide file location Details
Developers: the desired cube/report location on UniSAinfo Reporting
(Upfront) is specified above, however ISTS also need to know the specific
location of relevant files on \\itudev-bi1.
Required files are as follows: -
- PowerPlay cube .mdc
- PowerPlay Report .ppx and .mdc
- Impromptu Report .imr and .cat. (and location of .bmp file if image/logo is used)
15. Indicate Staff Portal visibility
Indicate whether the cube/report is to be viewable in the
UniSA Staff Portal.
Yes / No
If the report/cube is to be viewable then you will need to nominate the
relevant Search Categories
see UniSA Staff
Portal > My Management > Reports > Find a Report
Currently only cubes/reports viewable in UniSA Public are potentially available for viewing in the Staff Portal. (10-Nov-2008)
16. Notes
General comments:- eg indicate if a report needs to be made available in a
non default format eg xls
On completion of the publication form email the document to PAS by clicking on
request to publish on UniSAinfo Reporting (don't forget to attach the Publication Form to the email)
Should you require ISTS to handle automatic cube updating please email
ISTS by clicking on
request to organise automated cube update.

