Creating AppWorx Chains from Banner Processes and Reports

Presented by:

Loretta Sampson, Systems Analyst
Missouri State University Springfield, Missouri

Use Banner and In-House Objects within AppWorx

• Get Delivered Banner Reports into AppWorx Quickly • Launch in-house code and processes via AppWorx
– Presumes familiarity with BANNER Objects – Presumes familiarity with the product “AppWorx”


• BANNER and AppWorx are “business partners”
– This is why the “MKBANNER” process works as it does

• This session utilizes MSU “shop standards”
– “Shop Standards” are encouraged at any institution

• CHAIN is analogous to a JOB • MODULE is analogous to a STEP within a JOB

• Snapshot of the AppWorx window • The CHECK-MARK is the REQUEST screen

Navigate to the REQUESTS screen.e. Choose the module named “MKBANNER” – i.1. Make a Banner Report. Press “REQUEST…” .

The SUBMIT form displays. Double-click within the highlighted line to provide your selection(s). (a SUBMIT button is on this screen. just not clipped out here) . You might tag the job with your initials for easier identification if there are several queues.2.

FGRCASH is selected and moved. Choose the report(s) you are after. FGRTBEX is highlighted. MKBANNER will execute and finish. but not yet moved via the > button. The prior screen re-displays.3. . click the “SUBMIT” button. Click “OK”.

an AppWorx module exists with that same name. and default parameters of the BANNER module which was selected. At this point. This has the advantage of better “grouping” and “security” management by utilizing naming conventions. . description. Recap: Executing MKBANNER with the FGRCASH selection creates a mirror image of the BANNER / FGRCASH object called a module.4. but MSU has a standard of only executing chains. AppWorx modules may be executed (as the MKBANNER module was executed).

Banner modules download as being within the “BANNER” application. .5. We always keep the defaults associated with the “APPLICATION” and the “EXECUTION QUEUE”. we utilize our own). (For in-house modules.

but we’re doing the basics to get a report delivered. Now.6. On the “General” tab: 1 2 3 4 Leave BANNER as the default “Application” Leave the “Program” block defaults Leave the BANNER queue within the “Execution Options” block Select the appropriate “Notification” Here I choose GENERAL_ACCOUNTING Other NOTIFICATION options will need to be created – see HELP for that This can get “fancy”. . we EDIT this module.


– You may edit the date as shown. Now the “Prompts” tab. . This one only has SYSDATE. – Take all defaults. Some reports have many prompts.7. This will be done at the CHAIN level as well.

They may contain a value which can be overwritten.8. blank usually means “all”. Here is an example of several PROMPTS that come along when downloaded. Just leave them all alone. .

Now the ROLES tab. The module is ready – a module is a building block…. . MODULES will not be executed at MSU.9. Save your work. These are the three Roles that should be in our modules.

10. – Supply the appropriate prefix for the name – here it is FNS_FGRCASH – Select the appropriate Application – here it is FNS-RUN (continued below) . Navigate to the screen and choose NEW. While on the GENERAL tab…. To create a new CHAIN.

choose IMMEDIATE • If you think it does any processing in or out of BANNER.– Start the description with a word that describes the functionality. This technique will aid the Operators later on when they sort or search for a “type” of chain. choose HOLD – Everything else is defaulted . • • • • Report – a chain containing one report Reports – a chain containing more than one report Interface – a chain that interfaces with something else Process – a chain that performs Banner work/functions – Within EXECUTION OPTIONS • If you know it is a REPORT ONLY with no updating.

– Choose SUCCESSOR • It will hop over into your chain. Navigate to COMPONENTS – Choose the CHAINS/MODULES button – Slide down to the module you need..11. – This component is now a copy of the base module. Any fooling around happens within the component (copy) in the chain. . We always leave the base module alone. (Note the “M” in the “Type” column).


– When CHAINS are newly created they have no prompts. MODULE-level prompts are not accessible • PROMPTS must be copied from the module level to the chain level.level prompts are available to the user. it is the MODULE within the CHAIN that has the prompts. • Basically. we need to pass a parameter. . only CHAIN. • AND… the module level has to end up knowing about the value from the chain level. • BUT… when CHAINS are requested.Now it is time for a concept.

• Notice how the variable #SYSDATE in the MODULE is replaced by today’s date when submitting the CHAIN .

Choose OK. . Navigate to the module whose PROMPT(s) you want.12. At the CHAIN-PROMPT tab choose COPY 13.

When requested. It can be overwritten with a past or future date at that time. If not done before.14. Read more about system variables in HELP or the manual. Note. . here we have one (1) prompt. the job will display and default with the System Date.Here the SYSDATE is copied. SYSDATE must be edited to the system variable #SYSDATE.

1.And so on…they are typically in pairs.The chain-tabs remain at the top of the screen 2. .Choose the PROMPTS tab within the right-hand side. a.The component(module)-tabs are along the right-hand side.The second value from the chain replaces the second value in the component 3.The first value from the chain replaces the first value in the component 2.15. b. highlight the component to work with in the chain.Assign the VALUE column in tandem with the CHAIN prompt 1. At the CHAIN-COMPONENTS tab.

Choose a role from the bottom and press the ^ button.16. and DBA should always be assigned. . At the CHAIN-ROLES tab. The standard at MSU is that MISUSER-EDIT. we will assign the ROLE(s) that have permissions to execute this report – in this case FINANCE. OPERATOR-EDIT.

We will add ABORT CHAIN notes. check the box accordingly. MSU chains will often have four ROLES like this. 18. .17. and CHAIN notes. You may use HTML or not.

you can review what you are keying. By checking and unchecking the html box.19. just don’t use HTML at all). (Plain text can also be used. .

20. Describe important information about the CHAIN. . Repeat for the CHAIN notes.

(Request it just like you did with MKBANNER) .• Execute your chain and review the output.

• Congratulations! You now know how to create an APPWORX CHAIN! • Let’s see some general information and follow an in-house CHAIN with in-house MODULES .

• This is how you can easily find chains based on the application. or description. prefix. .

Our rule is to not execute modules directly.• This is where we keep our “support modules”. .

.• These are the modules that return from the MKBANNER execution. We take defaults.

• This in-house (customer-created) module is pointed to an in-house SQL: /home/appworx/library/sql/Z_CASHNET_MPP_SEM_DROP.sql .

Here is the GENERAL tab.• Let’s follow the CHAIN that will fire the previous module. .

• We are not doing anything special with OUTPUT at this time. .

• Let’s skip to the PROMPT tab. then a date and dollar amount to be supplied at execution time. • Note the “number” (placement) of the PROMPTS . • We have a default of AUDIT (which means no updating to MSU).

.• Back to the COMPONENTS tab. • The module PROMPTS (parameters) refer to the order of the chain PROMPTS • These prompts are evaluated within the sql. each module is fired in order as the CHAIN executes. Here are four modules – rather copies of modules – which are now components of this chain.

.• You can require that a prior module complete successfully before moving on.

• If we had used our POST prompt.• This module has a CONDITION. i. the last module would fire . not execute the last module. we want to CANCEL the CHAIN. • If we run this job with the chain’s AUDIT prompt.e.

• Back to the CHAIN tabs. . A SCHEDULE can execute a job as desired and also has several tabs.

.• The SCHEDULE for the chain can have a different set of PROMPTS. and be fired manually during the day with other criteria. • This chain can now fire each day with certain criteria.

• This CHAIN has no CONDITION. • We have created NOTES to help the Operators . so we will skip that tab.

annoying .• Several ROLES can execute this chain • People are assigned to ROLES • You can’t see more than four at a time.

• • • • Here is a complex chain for Financial Aid Several modules are called from the main chain Most of these modules are chains (sub-chains) Each sub-chain has it’s own set of prompts. et al. .

et al . • Each module within it has it’s own set of prompts.• Here is an expanded sub-chain. conditions.

• Here is another chain which has several conditions .

Permissions. or supply those for your own institution – Assign Roles. et al – Fire at will .• Recap for a Simple Chain: – Request and Submit MKBANNER to select and “pull down” delivered BANNER modules – Use that BANNER module as the only component for a chain (not required. Schedules. MSU Shop Standard) – Use default prompts (parameters).

Missouri .edu (417) 836-8710 Missouri State University Springfield. Systems Analyst LSampson@MissouriState.Thank you for attending! Questions? Loretta Sampson.

Sign up to vote on this title
UsefulNot useful