Proovongo 

Proovongo Documentation

Architectural Overview

PeopleSoft Installation

This chapter focuses on the steps necessary to load the Proovongo code into a PeopleSoft instance. Intended Audience: PeopleSoft Administrator, PeopleSoft Developer, and Security Administrator.

Proovongo

Import the Project Into PeopleSoft

There are several objects that need to be imported into the PeopleSoft database. These include necessary Integration Broker objects, application package code, and configuration pages.

The files necessary to import the code will be delivered to the contact person provided to Proovongo.

All of the objects in the project begin with either PROOVONGO or PRV. Some of the objects can be renamed though it is not recommended. Portions of the Application Package code indirectly reference the record names found in this project; any renames on Proovongo records will break the Application Package code.

Follow the instructions below to import the project manually into the PeopleSoft system.

  1. Locate the Project zip file that was provided by the Proovongo representative. The zip filename will contain the words “manual”, indicating it to be used for option A.
  2. Unzip this project zip file into a folder. The result should be two or more new folders, each starting with PROOVONGO. In the below example, the file was unzipped in the C:temp folder.
Proovongo

3. Open the Application Designer for the target database. It is recommended that the Proovongo project be first placed in a development or sandbox type of environment for testing purposes, before being deployed to a Production system.

4. From the menu, choose Tools →Copy Project →From File

 

Proovongo

5. Navigate to the folder where the project files are located.

6. The bottom most window contains all projects in the current folder. The project PROOVONGO_V101 should be in the list. Highlight that project and click the Select pushbutton. In a future step, other projects in this folder will be imported (such as PROOVONGO_V101_FSCM).

Proovongo
  1. The list of Definition Types should appear on the right hand side, with all types being selected by default.
  2. Deselect the Portal Registry Structures if you plan to manually create this item in Task 2. A Definition Type can be deselected by holding the Control key and then using the mouse to unselect the item. It is recommended that all Definition Types be imported in the first environment.
  3. Click Copy to import the objects into the target PeopleSoft database.
  4. The project is now viewable in Application Designer.
  5. Create the following records. If the database is Oracle, the record’s tablespace property may need to be modified. To build the project, select Build Project. The following are the three records in the project:

    A. PRV_SETUP_01
    B. PRV_SETUP_02
    C. PRV_SETUP_03

  6. Create all the views in the project.

Repeat the above steps and import other project files that begin with PROOVONGO_V101 and end with the appropriate system. For example, if the PeopleSoft instance has Finance and/or Supply Chain Management, import the project PROOVONGO_V101_FSCM. The project without the suffix is the base project, and is required. The projects with the suffix (such as FSCM or HCM) contain extra views that assist in the configuration of PROOVONGO for the appropriate application. For these project files, no new records need to be created; only the step to build the views is necessary.

Configure the Portal Structure and Content (Menu)

This task is most often done by a PeopeSoft Developer or the PeopeSoft Security Administrator.

If the option to import the Portal Registry Structures was selected in the previous task, this task can be skipped. The Proovongo folder will default to the root folder structure near the top of the menu as Proovongo Mobile Setup. The placement of this folder can then be moved to a sub-folder by the development or security staff, using the delivered tool Portal Structure and Content. Below represents how this folder and menu item should look by default (once security is granted, which is performed in the next task).

 

Proovongo

If the option to import the Portal Registry Structures was not selected in the previous task, the following steps are required to access the Portal menu where Proovongo configurations are performed.

  1. Log into the PeopleSoft PIA (web server) that has the Proovongo code that was imported.
  2. Navigate to PeopleTools→ Portal→ Structure and Content
  3. In the Structure and Content, navigate to the folder where the Proovongo Configuration page will be placed.
  4. Click the “Add Content Reference” action link.
  5. Populate the necessary fields as would normally be required when creating content.
  6. For the Menu and Component, use the following:
    1. Menu name is PROOVONGO_MENU
    2. Component name is PROOVONGO_SETUP
  7. Click Save when the page is completed.
Proovongo

Authorizing Security Access to the Configuration Page

This task is most often done by the PeopleSoft security administator.

By default, the permission list PROOVONGO_ADMIN and Role PROOVONGO_ADMIN are delivered with the Proovongo Project.

The Security Administrator will need to assign the Permission List PROOVONGO_ADMIN to an existing role, or assign the Role PROOVONGO_ADMIN to an existing userid.

The page that is being authorized will be used to configure which approvals will be accessed by the mobile devices. The page also allows configuration of which fields will appear for each approval type, as well as field order and field labels. This Role or Permission List access should be given to an Administrator or an end user who will be in charge of the configuration of Proovongo page. This user will be known as the PeopleSoft Proovongo Administrator in this guide.

Changes to the configuration page take effect immediately in the Proovongo Mobile App. Security to this page should be limited to a select group of users who understand the purpose of this page and the immediate effects of any changes performed on this page.

Integration Broker Setup

The Proovongo Project contains several Integration Broker objects. Below is a quick summary of the objects delivered:

  • Node: PROOVONGO_SERVER
  • Message: PROOVONGO_MESSAGE
  • Service: PROOVONGO_SERVICE
  • Service Operation: PROOVONGO_OPERATION
  • Routings: PROOVONGO_ROUTING

The Proovongo Mobile App can be run on mobile devices with or without VPN. If Proovongo will be configured on devices not requiring VPN, the Integration Broker setup will require a public gateway. This configuration will be covered in the next task.

The following steps need to be taken in order to allow the Proovongo Mobile App to access your PeopleSoft database, regardless of the public gateway setup being performed.

  1. Configure the Node PROOVONGO_SERVER
    1. Navigate to PeopleTools→ Integration Broker→ Integration Setup→ Nodes
    2. Open the Node PROOVONGO_SERVER.
    3. Ensure that the Active Node checkbox is checked.
    4. Change the Node Password to a new password.
    5. Change the Default User ID to a valid user id. Usually a system account can be used. The Proovongo Mobile App uses PeopleSoft userids and authentication, but utilizes a single userid (found on the page) to send message into the Proovongo Application Package code. In the Application Package, user authentication is performed
Proovongo

6. Navigate to the Connectors tab
7. Change the PrimaryURL property’s value.
8. Click Save.

2. Provide proper security access to the Service Operation PROOVONGO_OPERATION.

  1. Navigate to PeopleTools→ Integration Broker→ Integration Setup→ Service Operations
  2. Open the Service Operation PROOVONGO_OPERATION.
  3. Click the Service Operation Security link, as seen below. A new window should open.
Proovongo

4. Add the permission lists that will be allowed to access this Service Operations. It is recommended that a Permission List that the Default User ID can access be used here.

Proovongo

5. Click Save on the Web Service Access page, then close the window that was opened.

3. Configure the PROOVONGO_ROUTING

  1. Navigate to PeopleTools→ Integration Broker→ Integration Setup→ Service Operations
  2. Open the Service Operation PROOVONGO_OPERATION.
  3. Navigate to the Routings tab.
  4. Select the Routing PROOVONGO_ROUTING
  5. On the Routing Definition page, click the Graphical View
  6. Ensure that all connection points are active. If a link such as Integration Not Active appears, click the link to fix the issue encountered. The example below shows a routing where the Service Operation is not active. If no link appears in this area of the page, then no Integration Broker issues were found for the selected routing.
Proovongo

Integration Broker Public Gateway Setup

  • This task is necessary if the Proovongo Mobile App will be installed on mobile devices without VPN.
  • If VPN will be required to use the Proovongo Mobile App, then this step can be skipped.
  • Inteded Audience: PeopleSoft Administrator

PeopleSoft Proovongo Configuration

  • This chapter focuses on the Proovongo Configuration Page
  • Intended Audience: PeopleSoft Proovongo Administrator

Adding a New Proovongo Approval Process

Before an Approval Process can be configured in Proovongo, the Approval Process should be created and configured in PeopleSoft’s Approval Workflow Engine (AWE). There are many approval processes that are delivered with a PeopleSoft Application, but each must be configured.

The current release of Proovongo only supports approvals created and configured in AWE; it does not support the legacy process known as Virtual Approval.

Once the Approval Process is configured in AWE, follow the instructions below to connect each desired AWE to Proovongo:

  1. Log into the PeopleSoft PIA (web server) that has the Proovongo code that was imported.
  2. Navigate to the Proovongo Mobile Setup.
  3. Choose Add a New value
  4. Select the Approval Process that is being connected to Proovongo.
  5. Enter the Description and Long Description. At present, only the short description will be seen on the Proovongo Mobile App.
  6. Check the Comment Required on Deny checkbox if comments will be required if a Deny is initiated from the Proovongo Mobile App, for this Approval Process.
  7. Ensure that the Active field is checked.
  8. If the Approval Process being added already has the Header and Line Levels populated, that was performed automatically because the Approval Process chosen has a recommended view that was pre-built by the Proovongo Development team.
  9. If the record for the Header or Line are not pre-populated, follow the next step.
  10. For the Record (Table) Name field, choose a record definition that best defines the header record for this approval type. The only requirement is the record should contain the key fields that have been defined in the Approval Process as key fields. For example, the Approval Process “Purchase Order” could utilize PO_HDR as a record for the Header Level, since it has the main two key fields BUSINESS_UNIT and PO_ID. The configuration also allows a view to be created in Application Designer and utilized here. In addition, several views have been prebuilt by the Proovongo Development team and were loaded in the addendum projects (ending with FSCM, HCM, etc.) These prebuilt views from Proovongo begin with PRV_REC. If a search for any record beginning with PRV_REC is performed, the record description will show which approval process it is meant for. The pre-built views assist in giving translated values as well as linking to other tables, such as the vendor table.
  11. Once you select the record, the Field list will auto-populate.
  12. Click the Select checkbox to include a field on the Proovongo Mobile App.
  13. The Column Description field is currently for documentation purposes; future release may utilize this field on the Proovongo Mobile App.
  14. The Mobile App Order field can be changed to re-order the fields for the Proovongo Mobile App. As a user adds or changes this field, the Select checkbox and other fields in the order may change automatically.
Proovongo

15. The Sort Grid by Mobile App Order pushbutton will resort the fields in the current display.

 

Proovongo

 

16. To configure the Line Level record, go to the second row (the row count above the Sort Grid by Mobile App Order pushbutton).

17. The Setup Type should already be “Line Level”.

18. Choose the record or view that is appropriate for the Approval Process’s line level. The record should include the key fields necessary to match the transactions approval line level. If the Approval Process only has Header approval, a line level may still be desired.

19. Select Save once the configuration is complete.

 

 

Interested in getting started with Proovongo?

Next steps?


Learn More

View our 7 reasons to use Proovongo.


View Documentation

View the complete Proovongo documentation & Architectural.


Test Drive Proovongo

Register and we will send you a personalized test account.


Get a Quote

Contact us to disucuss your orginization’s needs and get a quote.

Why Partner With Bauen Solutions?

Bauen Solutions is a full-service tech and digital marketing company with services including mobile app and website development based in Houston, Texas. We focus on the unique needs of small to midsize businesses. The websites are built in a user friendly content management systems making it easy for your team to make updates or maintain a company blog. Our skilled developers create mobile apps using the Xamarin Platform. This makes for quicker development, easier maintenance, and an outstanding user experience, whether it’s Android, iPhone or Windows mobile phones. Our team focuses on your brand personality to create a professional, modern, easy to navigate, conversion-focused website or mobile app that is structured to build brand loyalty and growing your market.