1. © CGI Group Inc. Project Place and #define Version 0.2

2. What are #define and PrimePortal

3. #define #define is CGI’s production system for Application Management and Development, offered in the context of software as a service. It is a project management tool, configuration management system and collaborative workspace. #define is used by thousands of users on hundreds of CGI projects across the globe everyday.

4. PrimePortal To provide a more efficient means of communication between the delivery and client, CGI also develops and offers PrimePortal, a powerful tool that gives clients a transparent overview of the entire delivery. For migrating Project Place users, the main feature of interest in PrimePortal is the Document Manager. This gives the client access to a specific folder in the #define file archive, allowing them to download documents and share their own files with the delivery inside a client friendly and customisable interface.

5. #define File Archive

6. The File Archive Each #define project has its own file archive, where project members can upload files and share work with colleagues. To access your #define file archive click the Files tab in the ribbon. This will take you to the root of the file archive.

7. Navigating the File Archive In #define you can quickly navigate the file archive using the expandable sub directory feature. To do this click on the arrow head icon by the name of the directory you want to expand.

8. Previewing Files In #define a particularly useful feature is the inline source browser, which removes the need to download files before you preview their contents.

9. Creating Folders and Uploading Files In #define the options available to you on each page are usually displayed in the ribbon (this is the header of the web interface): Select the green Folder option to open a new dialog and create a folder. Select the green Upload File option to open a new dialog, select the appropriate file and upload it to your #define file archive.

10. Restricting Access In #define you can also restrict access to different directories and documents in the file archive using a path based permission system. If you have Project Mangers permissions this is configurable under Settings -> Administration -> File Archive Access. See our help guide for more information https://community.define.logica.com/help/DefineGuide/DefineBrowser#PathBasedP ermissions https://community.define.logica.com/help/DefineGuide/DefineBrowser#PathBasedP ermissions

11. Version Control Each #define file archive is technically a subversion repository. This provides you with extensive version control features which were not available in Project Place. What Is Subversion Subversion is a free version control system, which manages and records the changes made to the files stored in a Subversion repository. This includes changes to both individual changes and the overall repository structure. This means you can then view the differences between different versions of files, see who added particular lines and revert to previous versions of files if necessary.

12. TortoiseSVN To get the most out of the #define file archive and version control Subversion offers, you should download the Windows Explorer client TortoiseSVN. This is a free and popular Subversion client for Microsoft OS, whose main selling point is a user friendly interface. You can download it from http://tortoisesvn.net/http://tortoisesvn.net/

13. How to use Subversion and TortoiseSVN (1) To edit existing files stored in your subversion repository you have to perform a Checkout. This will download a copy of the files stored in your remote repository to your local machine (you can choose to checkout individual files, multiple directories or the entire repository if necessary). Any files you have checked-out to your local machine are known as Working Copies in Subversion. As the name suggests this is a copy of files downloaded from the central repository which you are free to work on and modify as you please, safe in the knowledge that any changes will not directly modify the central version of the file.

14. How to use Subversion and TortoiseSVN (2) To perform a checkout you need to know the appropriate base URL for your repository and the PATH to the particular directory or file you wish to checkout. To get this URL navigate to the appropriate directory or file in your #define file archive and click the Subversion URL option in the ribbon..

15. How to use Subversion and TortoiseSVN (3) On your local machine navigate to a directory using Windows Explorer and right click inside. In the dialog that appears ensure the value in the ‘URL of repository’ field is the same as the #define subversion URL you just copied from the project archive. To checkout the latest version of the repository make sure the ‘HEAD revision’ field is also select. Then press the OK button.

16. How to use Subversion and TortoiseSVN (4) A new window then appears highlighting which files are being downloaded. In this example only one file was downloaded and the checkout was successful, as noted by the ‘Completed’ action.

17. How to use Subversion and TortoiseSVN (5) In your directory you should now see all the files that were successful checked out. Next to each you should notice a small overlay icon, which indicate the status of each file. A green icon represents that the file has not been modified and matches the file held in the central project repository. All files freshly checked out should therefore have this green tick overlay icon.

18. How to use Subversion and TortoiseSVN (6) When you’ve finished editing a working copy of a file, you’ll want to upload it back to the #define file archive so other project members can view your work. This process of uploading a working copy back to the central archive is know as a Commit in Subversion terminology. To do this using TortoiseSVN navigate using Windows Explorer to the directory or file that you have previously checked out. You should note that after editing a file the Tortoise SVN overlay status icon will have changed from a green tick to a red exclamation mark. This signifies that the file has been modified.

19. How to use Subversion and TortoiseSVN (7) To share these changes with other project members right click on the directory and then select SVN Commit. The commit dialog that then appears has two important sections. In the first you can add a log message to describe the changes you’ve made. In the second section all the files which will be commited to the project archive are listed. Check this carefully before pressing OK, to ensure you are not committing the wrong files by mistake.

20. How to use Subversion and TortoiseSVN (8) Like when you checkout from the archive, a new window appears when you commit, showing the files which are being commited and the new revision number of the project archive if the commit is successful.

21. Revision Numbers and Changesets After a successful commit Subversion will display the latest revision number of the repository. This term and the phrase Changeset are often used interchangeably but there is a subtle and importance difference: A revision number identifies a snapshot of the repository at a single point in time. This is identifiable by a unique integer, which increments by one after each successful commit. A changeset identifies the specific changes made to particular files in the repository after a successful commit.

22. Publish To PrimePortal

23. Publish to PrimePortal In your #define file archive there is a special folder called PrimePortal. All the files you place in this directory are published to PrimePortal. You can upload documents to this directory using the Upload File feature in the web interface or using the TortoiseSVN client.

24. Publish to PrimePortal This means that these files are accessible to the client side of the delivery in the PrimePortal web interface. Users who only have PrimePortal access can also upload documents to share with users in the #define project.

25. PrimePortal Document Archive

26. Accessing The Document Archive To access the document archive in the PrimePortal web interface you should select the Documents option from your project tab.

27. Uploading Files and Creating Folders To upload a new file or create a new directory you should select the Upload Files or Create Folder option.

28. Uploading Files and Creating Folders You can also use TortoiseSVN to perform more advanced file operations, as the PrimePortal document archive is just a directory of the #define Subversion repository. To use TortoiseSVN you must request that we show the Subversion URL inside the PrimePortal web interface. To do this you should contact servicedesk@logica.com

29. Document Information You can see who made the last change to each file by focusing on the revision author column. The last modified date, revision number and file size are also displayed in the table.

30. Searching The Document Archive There is also a quick filter search option available, where the results of the search are displayed without refreshing the page.

31. Downloading Files To download a file from the document archive, hover your cursor over the name of the file and select the drop down list icon that appears. Then click Download.

32. Additional PrimePortal Features

33. Contacts To ensure everyone in your team has the right contact information for other team members and the client, PrimePortal includes a dedicated Contacts page. Users with the infomaster role can click the Add New Item link to add more contact details.

34. Contacts (2) You can also export contact details in a Virtual Contact File. Just hover your cursor over the appropriate contact name, open the drop down list and select Export Contact.

35. Calendar There is also a calendar feature available inside PrimePortal, where users can share meeting, event and deadline details with other project members.

36. Calendar (2) Users in the infomaster access group can add a new event to your project calendar by selecting the New dropdown option in the top left of the calendar window and selecting New Item.

37. Additional #define Features

38. Other Components Issue Tracker: all types of work can be documented in tickets and managed by the issue tracker. Ticket types, layouts and workflows are fully customisable to meet individual requirements. A powerful query builder allows users to search for tickets and returns the results in various formats. Wiki Pages: version controlled wiki pages are a centralised source of information which inspire collaboration and a sense of ownership. They are a rapid and efficient way of maintaining and sharing content with other employees. Planning: you can assign work to particular milestones and view a high level, graphical summary of progress on the roadmap page. This allows projects to plan ahead and anticipate potential problems before they impact the delivery. Mailing Lists: often used as discussion board for different interest groups, mailing lists are a powerful way to distribute project related information. All messages sent to a mailing list are stored in a fully searchable archive to increase traceability.

39. Source Code #define is often used by projects who write code as part of their delivery. Consequently #define has been designed and developed to manage source code in a user friendly way. For example, the inline source browser includes syntax highlighting capabilities to make source code more readable and an annotate feature which displays the author and changeset which last modified each line in a file.

40. #define User Management

41. Membership Groups (1) In #define users can be placed into membership groups. These groups have varying levels of permissions. The three default groups in descending level of permissions are: Project Managers Project Members Project Viewers You should only add users to the project managers group who need access to the administrative settings of #define. In general most users should be added to the project members group. They will then be able to access the file archive, upload files, create tickets, edit wiki page etc. Remember - A user must be in a membership group for them to access your #define project.

42. Membership Groups (2) To view your project membership groups: 1. Select the Settings tab 2. Select the Administration drop down 3. Select the Access and Groups page

43. Membership Groups (3) To add a user to a project group you must have project manager permissions. The project infomaster will have these permissions. 1. Select the Settings tab 2. Select the Administration drop down 3. Select the Access and Groups page 4. Select a membership group name 5. Select the Add User button If the user has a GROUPINFRA or ACC account, enter their username details, select the user and press Add If the user does not have a GROUPINFRA or ACC account you need to create an external user account. You can do this by selecting the Creating External user button the same page.

44. Membership Groups (4) You can also create your own groups, with customisable names and permission settings. 1. Select the Settings tab 2. Select the Administration drop down 3. Select the Access and Groups page 4. Select the Add Group button 5. Complete the dialog form

45. Membership Groups (5) On the subsequent page you need to configure the Group Permissions settings. Here you should select which group you want to replicate the permissions of. This is likely to be Project Members or Project Viewers. Do not select Project Managers unless you want members of this new group to have access to the administrative components of #define.

46. PrimePortal User Management

47. User Management (1) To access user management settings in PrimePortal you need to access the User Administration interface via the navigational menu. Note only specified users will have permission to access this component.

48. User Management (2) To add a user click the New User button on the User Administration page. You should then select an appropriate domain – local for external users and groupinfra for CGI employees.

49. User Management (3) Next fill in the required fields and select which group to place the user in. You should only add users to Project Admin or Infomaster groups if you want them to access important administrative and configuration components. For most users you will want to add them to Project Write – they will then be able to view and upload files to the Document Archive.

50. User Management (4) You can view which users have access to your PrimePortal instance by selecting the Show Users button on the User administration page. You can also filter these results based on the users name, email address, user id or domain group.

51. Our commitment to you We approach every engagement with one objective in mind: to help clients succeed 51