OpenMake Meister

Configure Tab Screen

 

The Configure Tab screen displays four sections: General Information, Execute Settings, Schedule Information, and Configure Environment. These four sections contain the attributes associated with a Workflow

 

General Information Section

 

Public or Private

A Workflow can be designated as either Public or Private.  All users can execute a Workflow that is designated as Public, whereas a Workflow that is designated as Private allows only the original creator to execute the Workflow.  Users that have read and write privileges for a Workflow can change the Workflow. The creator of a Workflow can change a Public Workflow back to a Private Workflow, and any Administrator can change any Public Workflow to a Private Workflow.

 

Workflow Name

The Workflow Name is a label that references the name of the Workflow and indicates relevant information about its state, for example, APPL1 - NIGHTLY INTEGRATION BUILD.  Use the Workflow Name field to enter the name of a specific Workflow as you want it to appear on the list of executable Workflows.

 

Workflow Job Number

A pattern of letters is used to label an instance of a Workflow execution. As  Workflows are executed multiple times, each execution is given a unique indentifying job number. This job number is generated by default and can be customized by user-defined expressions.  This Workflow Job Number will then appear on the Workflow Monitor when the Workflow is executed and will be available through the $(JOB_NUMBER) macro for generating activities within individual Workflows.

 

When creating user-defined expressions for Workflow Job Numbers, the date or time component and/or an index number can be updated along with any other text that you would like to include.  The fields that you choose to update need to be placed in square brackets.  These fields can be designated either by a number to be incremented by one or by letters that signify date and time information. All data must be input as valid SimpleDateFormat strings. 

 

Table WM-2 shows you how to form valid SimpleDateFormat strings (from https://java.sun.com/javase/6/docs/api/java/text/SimpleDateFormat.html, Java Platform SE 6, Sun Microsystems).

 

Table WM-2. Simple Date Format Strings for a Workflow Job Number Pattern

Letter

Date or Time Component

Component

Examples

G

Era designator

Text

AD

y

Year

Year

1996; 96

M

Month in year

Month

July; Jul; 07

w

Week in year

Number

27

W

Week in month

Number

2

D

Day in year

Number

189

d

Day in month

Number

10

E

Day in week

Text

Tuesday; Tue

a

AM/PM marker

Text

PM

H

Hour in day (0-23)

Number

0

k

Hour in day (1-24)

Number

24

K

Hour in AM/PM (0-11)

Number

0

h

Hour in AM/PM (1-12)

Number

12

m

Minute in hour

Number

30

s

Second in minute

Number

55

S

Millisecond

Number

978

z

Time zone

General time zone

Pacific Standard Time; PST; GMT-08:00

Z

Time zone

RFC 822 time zone

-0800

 

Pattern letters are typically repeated within each string, and the number of pattern letters determines the exact presentation in the Workflow Monitor, as shown in Table WM-3. Table WM-4 includes examples of how date and time patterns are interpreted in the U.S. locale. The example date (2001-07-04) and time (12:08:56 local time) are from U.S. Pacific Daylight Time (PDT).

 

Table WM-3. Presentation of Pattern Letters as Determined by Their Number

 

Formatting

Parsing

Text

If the number of pattern letters is 4 or more, the full form is used; otherwise, a short or abbreviated form is used, if available.

Both forms are accepted, independent of the number of pattern letters.

Number

The number of pattern letters is the minimum number of digits, and shorter numbers are zero-padded to this amount.

The number of pattern letters is ignored unless it is needed to separate two adjacent fields.

Year

If the number of pattern letters is 2, the year is truncated to 2 digits; otherwise, it is interpreted as a number.

If the number of pattern letters is more than 2, the year is interpreted literally, regardless of the number of digits. So using the pattern "MM/dd/yyyy", "01/11/12" parses to Jan 11, 12 A.D.

Month

If the number of pattern letters is 3 or more, the month is interpreted as text; otherwise, it is interpreted as a number.

None.

General Time Zone

Time zones are interpreted as text if they have names. For time zones representing a GMT offset value, use the following syntax:

GMT Sign Hours:Minutes,  where

Sign is one of  + or – ;

Hours takes the form of either Digit or Digit Digit;

Minutes takes the form of Digit Digit;

Hours must be between 0 and 23; and

Minutes must be between 00 and 59.

The format is locale independent, and digits must be taken from Unicode Characters in the Basic Latin Block.

RFC 822 time zones are accepted.

 

RFC 822 Time Zone

The RFC 822 four-digit time-zone format is Sign TwoDigitHours Minutes. The TwoDigitHours format must be between 00 and 23. Other definitions are the same as for general time zones.

General time zones are accepted.

 

 

 

Table WM-4. Date and Time Pattern Examples as Interpreted in the U.S. Locale

Date and Time Pattern

Result

"yyyy.MM.dd G 'at' HH:mm:ss z"

2001.07.04 AD at 12:08:56 PDT

"EEE, MMM d, ' 'yy"

Wed, Jul 4, '01

"hh 'o' 'clock' a, zzzz"

12 o'clock PM, Pacific Daylight Time

"yyyyy.MMMM.dd GGG hh:mm aaa"

02001.July.04 AD 12:08 PM

"EEE, d MMM yyyy HH:mm:ss Z"

Wed, 4 Jul 2001 12:08:56 -0700

"yyMMddHHmmssZ"

010704120856-0700

 

Workflow Job Label

The Workflow Job Label is a short description of the Workflow’s purpose and specifications, for example, Weekly integration build for project lead or Takes updates from CVS and promotes successful build to testing.  Any relevant information about the Workflow that cannot make it into the Workflow Name field should be entered here.