PerfectForms and ESIGN Promotions

This page will describe the steps on how to promote new or converted PerfectForms to Production.

• Log into both the TEST and PROD database session (ie Toad)
• Open an Editor and Schema Browser sessions

Background

Based on the type of promotion you may need to INSERT or UPDATE one or more tables.

Check to see if this form is a new or converted form. If the form had an "old forms" version it is being converted.

• Old forms ==> WEBMENU_IDs range (< 1000)

• Converted forms ==> WEBMENU_IDs range (between 1000 and 1999)

• New forms ==> WEBMENU_IDs range (>= 2000)

Query the TEST ESIGN.WEBMENU table.

They should give the WEBMENU_ID in the ticket, but if they don't, you'll have to query the table.

Check the ESIGN.WEBMENU table for a WEBMENU_TITLE that matches the new menu item.

Examples of Filters:

1. upper(WEBMENU_TITLE) like upper('%CHECKLIST%')
2. WEBMENU_ID = 2040
3. WEBMENU_TITLE like '%MSDNA%' or WEBMENU_DESC like '%MSDNA%'

Are there more than one match?

• If yes, look at the WEBMENU_ID numbers.
• If there is an "old" WEBMENU_ID, then the converted number needs to be in the 1000 range, but have the 3-digit the same.

  • Ex. Old = 176, Converted = 1176

• If there is no "old" WEBMENU_ID, then it is a New form.

Promotion of ESIGN Perfect Forms to PRODUCTION

If there is a single or a few changes it can be handled manually (see Manual Process).

However, if there are more that a couple changes, the Developer should perform the following to build a set of instructions / statements (see Scripted or Execution Instructions).

Manual Process

New Form Steps -

The new range should be in the 2000's.

• Look at the WEBMENU_ID number they assigned.
• Make sure it is not already used and falls into the next series (or close).
• Ex. New = 2040

The easiest way to promote is to:

• Copy the TEST row, generating an INSERT statement.
• Paste the INSERT statement into the PROD window.
• Make sure the WEBMENU_ID is ok and UPDATE the URL with the URL provided in the Ticket.
• This insures that TEST and PROD are insync, but have the correct URLs for each environment.

Generating an INSERT statement:

• With TOAD, you can filter on the specific WEBMENU_ID, right click and "EXPORT DATASET".
  • Ex. upper(webmenu_title) like upper('%checklist%') and webmenu_id = 2040
  In the "Export format" at the top, click on "Insert Statements" and click OK.

Switch to the PROD SQL-Editor window and paste.

• Insert into ESIGN.WEBMENU
  • (WEBMENU_ID, WEBMENU_TITLE, WEBMENU_DESC, WEBMENU_ALPHA, WEBMENU_WEBTYPE_ID,
  • WEBMENU_WEBDEPT_ID, WEBMENU_URL, WEBMENU_IS_STUDENT)
• Values

  • (2040, '<b>Checklist for lost, stolen or missing Devices Request</b>', 'Checklist for lost, stolen or missing Devices Request', 'C', 10,

  • 2167, 'https://eformstest.oakland.edu/perfectformsSSO/player.htm?f=rFBgAgEC', 'N');

• COMMIT;

YOU MUST update the URL.

MANY, MANY, MANY times, the Description in TEST does NOT exactly match what they put in the Ticket.

Therefore, UPATE the Title and Menu in TEST and in the PROD Insert statement as well.

• Insert into ESIGN.WEBMENU
  • (WEBMENU_ID, WEBMENU_TITLE, WEBMENU_DESC, WEBMENU_ALPHA, WEBMENU_WEBTYPE_ID,
  • WEBMENU_WEBDEPT_ID, WEBMENU_URL, WEBMENU_IS_STUDENT)
• Values

  • (2040, '<b>Checklist for Lost, Stolen or Missing Computer, Smartphone or Other Media Storage Devices</b>', 'Checklist for Lost, Stolen or Missing Computer, Smartphone or Other Media Storage Devices', 'C', 10,

  • 2167, 'https://eforms.oakland.edu/PerfectFormsSSO/player.htm?f=emAgAgQk', 'N');

• COMMIT;

Convert Forms Steps -

The Convert is similar to the New. For the WEBMENU_ID, use the Old Webmenu_id + 1000 = New Webmenu_id Check to make sure it isn't being used. It should not be.

Follow New Form Steps

After the INSERT to the WEBMENU table (as with New), you will need to update the WEBFILE row for the OLD menu item. They should give you the FILENO for the old item. If they don't, you can try to search looking at the Path and Name. Once you find the correct row, UPDATE the FIELDNAMES value.

Append 'OBSOLETE,' to the end (w/o quotes) of the existing value.

Commit.

Update Footprints Ticket -

After the INSERT and COMMIT in PROD (and in TEST if needed), update and close the Footprints Ticket.

Scripted or Execution Instructions

1. From the Schema Browser, view each table using TOAD in TEST.

2. Using "filter", display only the rows that need to be changed a. Example of filter for WEBMENU table

• webmenu_id = 130 and upper(webmenu_title) like upper('%MSDNAA%')

b. Example of filter for WEBFILE table --upper(NAME) LIKE '%MSDNA%' --fileno = 126

3. Once result is returned and verified, use Export Dataset to capture the changes. a. Right-click on the results and click on "Export Dataset" b. In the "Export format" drop-down, select "Insert Statements" c. The other settings on this panel should be - - Output = Clipboard - Display all results in grid - checked - Include schema name - checked - Automatically detect schema and name - checked d. Click OK

4. Paste (ctrl-v) the clipboard contents into the Footprints Ticket OR into a script text file and attach to the Footprints Ticket.

Insert into ESIGN.WEBMENU

• (WEBMENU_ID, WEBMENU_TITLE, WEBMENU_DESC, WEBMENU_ALPHA, WEBMENU_WEBTYPE_ID,
  • WEBMENU_WEBDEPT_ID, WEBMENU_URL, WEBMENU_IS_STUDENT)

• Values

  • (130, '<b>MSDNAA Student Account Request(No Login)</b>', 'MSDNAA Student Account Request', 'M', 10,

    • 30, 'http://eformstest.oakland.edu/PerfectForms/player.htm?f=zKAgAgUD', 'N');

COMMIT;

5. Change any specific data values the were in TEST, but MUST be different in PROD. a. Change the URL value from "eformstest.oakland...." to value for PROD "eforms.oakland..".

6. Note whether this is a NEW row or an EXISTING row in PROD. a. If it is EXISTING, include the DELETE for the row

DELETE ESIGN.WEBMENU WHERE WEBMENU_ID = 130;

DataAdminHowTo