WebLogic Administrator Interview Questions

Q: What do you mean by weighted based server instance? How do you configure it?

Ans: The Weblogic Servers in a cluster environment could be routed in 4 ways ROUND-ROBINWEIGHT-BASEDRANDOM We can control the incoming requests using weights increase or decrease, So, that all the request will goes to one particular managed server only that too possible.

Q: How to enable EJB available to servlet? asume servlet on apache, ejb on Weblogic cluster.

Ans:Any external access to EJB is not allowed. if the apache webserver already configure as front-end. then we need to look up by JNDI tree.

Q: What is the silent mode installation file contains root element? When do you require this mode of installation?

Ans:The root element in silent.xml is <install>This kind of mode usually required in two different situations.

Situation1 : Weblogic clusters could be installed/implemented only on homogenous environments. If cluster1 is constructed with MgdServer1, MgdServer2if one server isusing Weblogic 7 environment and other one on Weblogic 8.1 or higher this is not allowed.

Situation 2: When one huge project is migrated from one physical location to other, Where the Application specialist must have the similar environment as the Production Server had. To prepare Development work with similar kind environment we shall install on First system same as Production Server rest of the developers systems could be installed with silent mode.

Q: Why do you need multicast address in Clustering?

Ans: The Multicast address is must for clustering, If server instance need to join the cluster it will use multicast address. The Administrator server handles the web/resource request which is incoming to the Weblogic server then the admin server will send poll messages for availability to handle the current incoming request by which member server in the cluster with multicasting. The multicast address should not conflict with the Network configurations on every member server. The range of multicast IP address is : 224.0.0.0 to 239.255.255.255.The admin server sends a TTL (Time to Leave) packet,which will acknowledges the readiness of a managed server. If more than one member server is available then it will choose the member server with first come first server bases.

Q: What are all the ant command options?

Ans:To view all options of ant command is simple, just use the following command :prompt> ant -helpNote: This will work on Unix and Windows too iff PATH is pointing to ant specific jars

Q: What is the ant version last you used? How to get it??

Ans: I am using Weblogic 8.1 it internally provides ant support which is 1.5.6 version.To get this simply use : prompt> ant -version

Q: How do you config eclipse with Weblogic?

Ans:Weblogic version wise plug-ins are available for free download sites. Eg: lomboz tool it is a very simple tool, my experience is that deployment on WL is very few steps required.Just we need to copy the plug-in extracted to eclipse/plug-ins folder. Here we need to follow the correct J2EE specification for easy deployments of application.

Q: what is the source to identifying the Connection pool failure? What is the remedy?

Ans: In WL 7/8 to identify the connection pool failure we have 3 options: 1.The Connection pool hosting Server instance healthchecking by Monitoring tab where we need to find the idle thread availability.2. Checking in the weblogic log of that corresponding server instance. Usually we get broken pipe Exception.This could be generated due to overload on connection pool. To resolve we can tune the execute threads for the corresponding server instance.3. Look for Thread dump and identify the which thread is doing which task execution?

Q: What is thread dump? Why we need it? How do we get it?

Ans:Thread dump concept is used only by Admin users who operates the production server; it is the dump of the behavior of the WebLogic server instance’s execute threads.When the thread dumps helpful? If WLS execute threads misbehaving due to following reasonsMaybe you just need more threads. Maybe you need some of your application to use a different queue. Maybe your application needs tuning.There is a need of trouble shoots the issues due to various reasons: 1. Requests overloaded2. Connection Pool fails3. File cannot read/write for any application (which might be xml file too)4.Queues are overloadedIn windows CTRL + Break , There is another common method to get thread dump:a) Open a cmd window (in Windows) or shell (in Unix/Linux)b) Set the proper java path and add weblogic.jar to the classpathc) Run the following command script :prompt >java weblogic.Admin -url t3://host:port -username weblogic -password weblogic THREAD_DUMP Here please replace with the correct host, port number, username and password. You can get the thread dump from the standard output.

Q: What is the procedure for Queues config? How to make them to free?

Ans:The Queues configuration requires persistence storage which could be a File on operating system or a Database. The queue configuration requires JMSConnectionFactory, JMSServer, Queue or topic as per the need for the application created using the Weblogic Administration console.

Q: What is the architecture you follow for your current project?

Ans: DMZ ( webserver-weblogic-database) with Multi- tiered architecture where in the first level of request could be handled by CISCO CSS to Apache webserver instances then next to WebLogic domains as per the application requirements the Oracle database is configured thru connecton pools. going forward Middle ware server as Tuxedo server connecting to Mainframe based Database Server where the billing system resides.

Q: Do you required JDK/JRE for installing a WL Domain?

Yes, JRE is required to run the Configuration Wizard in GUI. if the domain configuration is in the console mode or silent mode it is not required. Some Unix flavour OS does not have JRE in built so we need to install JDK/JRE before the WL domain creation. It is one of the pre-requisite for domain creation.

Q: What is the basic requirement for starting a Weblogic server?

Ans:The basic requirement for starting WLS is ... If you need to start service like web application/enterprise application we must start the WebLogic server instances. These services requires the server to be running state then only they can serve the client request. The server instances would be one of the targets for deployment of services. If I have a jar file and a war file how do you design your WebLogic server configuration?That depends on the version dmconf, config executable file(s) which gives us configuration wizard to configure the Weblogic server(s) on the domain and with option to create cluster env.

Q: Why do you feel that there is need for webserver like Apache as frontend before to WebLogic?

The Weblogic server alone acts as group of server instances if one of the request might lead to down the server then whole applicatons goes down. in the safer sinario we use Apache as sheld from Web. Apache is most powerful in tranfering the Images, CSS, Html related scripts on the fly... the apache just hold the images or .css or .js files in the cache when new web client request will be executed faster compare to Weblogic webserver

                                   WIPRO AND ORACLE

1. Describe yourself about your daily activities @ work

2. What is the way to find the impact on the database connection changes on a server instance?

3. How do you identify the Server instance is overloaded? (Idle Threads)

4. How do you connect to ORACLE RAC with WebLogic Connection Pool?

5. How do you do create Thread Dump?(kill -3 refer above)

6. How the message are generate into the monitoring tool?

7. Usually which language you prefer to write code like options are Jacl/Python/?

8. What is JVM?

9. What is the EJB?

10.How do you measure the heap size of a WebLogic server?

                                     Basic Unix

1. How do you copy files from onemachine to other? (scp/sftp/ftp)

2. How do you take the backup of the files to tape drive?

3. How do you create a directory? (mkdir)

4. vi - how do you search for a word?  : name work

5. vi - how do you replace words? n word

6. vi - save a file how? (:wq or :w or ZZ)

7. Which scripting shell you have used?

8. How do you export a env variable in a shell script?

9. How do you check the script is already existing or not?

10. How do watch the memory size for a the mounted devices ? (df -k)

Database/Oracle

1. How do you connect to Oracle database? discuss on connection pool configuration?.

2.How do you get the total count of the records in a table?

3.How do you delete a row in a table?

                                              (Verizon)

1. You need to handle whole and sole responsibilities to handle WebLogic Admin activities are you ready to accept?

2. What is the experiance with WebLogic Administration activities you do in last project/current project?

3. What is a cluster? What is High Availability and Fail over?

4. What is the major difference between managed server and admin server?

5. What is the difference between Connection Pool and datasource?

6. Do the user can use Connection pool in their program?

7. How do you configure ORACLE RAC env to WebLogic Connection Pool? What are the conditions applied for this?

8. How do you use weblogic.Admin tool? what for it is used?

9. What is the Thread Dump? when do you need it? What do you analyze from thread dumps?

10. What is a web server? how it is different from Application server?

11. What is level of comfort in architecturing/designing?

                                        Second round:

1. What do you mean by multipool? how does it differ from connection pools?

2. Have ever worked on tuning of the weblogic?

3. Have you ever installed weblogic on UNIX env? Have you installed from a CD?

4. Why do you choose Type-4 driver instead of Type-2? What are the features of type-4 driver?

5. When do you go for Weblogic jDriver? What advantages with jDriver?

6. What is the recent Exception you had faced in troubleshooting activity?

7. Do you ever experianced the Webserver configuration for Weblogic?

8. Do you have the steps to implement IIS webserver for Weblogic 9 Server?

9. Do you have any idea about WLI, WebLogic Portals?

10. What is the difference in normal Weblogic JMS and WLI JMS queues?

11. What kind of preventions you take for troubleshooting? How do you proceed in the finding the culprit?

                              Scripting Related Questions

1. Do you know how to write a script?

2. Have you ever written scheduled jobs?

3. Have you ever written rc scripts?

4. Which version of Solaris you have been worked?

5. If you have given high severity script to update how do you do that?

Simple take the help of the team members. If the solutions is not found I will look into internet group/blogs thru search engine.

6. Have you ever written any schedule scripts?I got chance to work on scheduled script only few times. I said myself very little experience in using crontab.

7. How do you assign a cron job?

Ans: Using crontab command followed by the cron scheduler file which says what script/program to be executed at what time.

 

.

PegaCALL for PegaRULES

The below link explain about PegaCALL for PegaRULES:

PegaCALL provides Computer Telephony Integration (CTI) to improve contact center operations. PegaCALL integrates with telephone switches (traditionally called Private Branch Exchanges or PBXs) and Interactive Voice Response Units (IVRs and VRUs) to enhance telephone-based customer interactions such as service inquiries, telemarketing, sales, and collection efforts, increasing agent productivity and enhancing customer satisfaction




https://pdn.pega.com/products/pegacall-for-pegarules

Backward chaining in Pega

Backward chaining executes declare expression rules when a value is needed for a property, as opposed to when inputs change. For example, a value may be needed because a property’s value is referenced in an HTML stream for display.

Backward chaining applies to declare expressions rules with the Calculate Value field set to one of the following:

• When used if no value present
• When used, if property is missing
• Whenever used

Think of it like this … the system says “I need property X, if it isn’t there, calculate it for me”.

For example: Area = Length x Width and is set up for backward chaining with the “Whenever used” option set on the Area property.  If you try to display Area (even just in the property rule preview), the declare expression rule re-computes. This re-computation is driven by the use or referencing of Area, not by any changes in Length or Width.

If a value for Area is needed through backward chaining, but Length has no value, the chaining may continue using a declare expression rule to calculate Length, and so on.  Alternatively, the application can prompt a user to enter a value.

Experiment with backward chaining using the following standard rules

• Work-.VerifyProperty flow action
• Work-.VerifyPropertywithListing flow action
• Work-.PromptGoalSeekProperty HTML rule
• Work-.VerifyProperty activity

The Property-Seek-Value method is the foundation of backward-chained processing. What is really important to understand is that the system will only execute the required calculations as needed, which can result in huge efficiency gains

Let’s look at the conditional display of a Volume property.  If the Volume property is displayed, the expression for the calculation of its value fires – backward chaining.

If the harness does not display Volume (set by a When rule), calculation is not necessary and valuable system resources are saved as a result.

Just imagine if the retrieval and calculation processing of this data had a cost, either literally or just in terms of time and system resources.  With a procedural design model you would have to either code a lot of if/else statements to micro manage things, or waste valuable time and money processing data needlessly.

For more information on backward chaining, refer to PDN and Developer Help topics on Locate Pages, Locate Activities and Declare Pages, as well as the e-Learning course on Declarative Pages

Using the Case Manager Portal 6.2

The Case Manager portal provides users (who are sometimes called caseworkers) with a standard user interface for:

• Creating, viewing, and working on cases
• Displaying unresolved cases, their subcases, and a case's open assignments
• Displaying associated content, users, roles, and subjects
• Monitoring work group status, goals, and deadlines
• Generating work management reports

In V6.2, the Case Manager portal is the default portal for applications created with the Application Accelerator, and is recommended for new applications.

This article describes the portal's facilities and features.

Case Manager portal
 
The Case Manager portal (pyCaseManager portal) comprises four tabs:
The My Dashboard tab provides work statistics and data for work groups, individual operators, and workbaskets

1. The My Cases tab contains information about work items (cases) associated with case types defined in the Case Designer gadget on the Case Management landing page.
2. The My Events tab lets users monitor business events, and view upcoming goals and deadlines.
3. The My Reports tab provides the Report Browser, which displays reports available to the user based on report definition rules, and may also display List View and Summary View reports.

My Dashboard

This tab (Data-Portal.pyDashboard harness) provides four views of work statistics and data for:
A work group

• Operators within a work group
• A summary of all workbaskets in an application
• Individual workbaskets

Here is an example of the portal in the work group view

A navigation tree in the left panel enables users to select and open each view. The tree can also be used to transfer work among operators and workbaskets. The tree has two top nodes: Work Group and Workbaskets.
Selecting a time interval — Using links at the top-right corner of the center work area, the user can filter work statistics for the following time periods: today, this week, this month, this quarter, last 7 days, last 30 days, or last 90 days.
Work Group — The name of the work group appears next to the icon. The user clicks the icon to display a list of work group operator names below the top node. The number next to each name indicates the operator's total number of assignments. A name in bold text indicates that the user is the Manager (Sandra Glover in the above example) defined in the Work Group rule form.

The work group view contains two sections:
Summary
For the select time interval:

• Case Completion Rate speedometer — Shows, as a percentage, the work group's throughput of resolved work based on the number of created and open cases.
• Open Case Timeliness speedometer — Shows, as a percentage, the number of work group cases that are within goal (based upon assignment SLA-related data).
• Top Performers list — Displays the five operators who have resolved the most cases and related statistics.
• Case Volume graph — Displays trend lines for new and resolved cases.

Recently Resolved

For the selected time interval:
Displays the 50 cases most recently resolved by the users in the work group. Click a work item's ID to open the case's review form.

Clicking an operator name in the tree to display a view of the operator's work statistics:

The operator area contains two sections:

My Work <or operator 's name> Work for <selected time interval>

• Case Completion speedometer — Shows, as a percentage, the operator's throughput of resolved work based on the number of created and open cases.
• Open Case Timeliness speedometer — Shows, as a percentage, the amount of the operator's work that is within goal (based on assignment SLA-related data).
• Performance — Indicates the operator's numerical standing among the other operators in terms of cases resolved.

Urgent Work —Displays the top 25  case assignments that have the highest urgency values. You can copy and customize the report definition Assign-pyAssignmentWorkList to suit your requirements. By default, the maximum number of cases displayed is 500, which is set in the Maximum Number of Rows to Retrieve field on the report's Data Access tab.
 
Users can transfer assignments by dragging the item's row header from the user's work list to an operator or workbasket in the navigation tree.

Workbaskets — The user clicks the icon to display, in the summary workbaskets dashboard, a list of urgent work items for all workbaskets in the application.




Clicking the name of a workbasket in the tree to open its list of urgent work items. The numeric value next to the workbasket name indicates the number of assignments in the workbasket. Users can transfer work between workbaskets using the drag-and-drop transfer feature.

My Cases

This tab (Data-Portal.pyCMCases harness) initially displays, in the top-level nodes of a tree grid, all cases where the following are true:

• The case is in one of the operator's work pools, is not resolved, and is not covered by another case.
• The current operator is a party to that case. The node does not appear if the current operator is a party to only a subcase but not to the top-level case.

The user selects a case to expand it and display its subcases. In the example below, the Loans case has two subcases: Background Check and Underwrite.

Selecting a subcase displays, in an embedded pane beneath the grid, the user form's work summary section (pyWorkSummary). The user can click the breadcrumb link in the header to open the parent case in its user form.





The system uses the standard report definition Work-.MyCasesReport to display the he top-level cases. By default, the maximum number of cases is 500; the value is set in the Maximum Number of Rows to Retrieve field on the report's Data Access tab. When the user expands a case to display its children, the system the Work- pyLoadMyCasesNested report, which has a default limit of 500 subcases.

The user can perform actions on a case or subcase by right-clicking the item in the tree.

• Open — Opens the case's user form in a portal tab.
• Complete Item — Resolves this case (assuming it has no required and unresolved subcase(s)).
• Withdraw Item — Reject and withdraw this case.
• Actions — Lists the connector ( ) and local ( ) flow actions for this case. Selecting an item opens its user form.
• Create Ad Hoc Work — Under the parent case, create a subcase and start a work process that is not defined as a case type in the application structure. When the user selects this option, a modal dialog opens and presents a new work form for entering goals and deadline SLA information. The user can select either of two standard ad hoc processes. When the user creates the ad hoc case, it appears in the tree indicated by an ad hoc work icon (). With the required permission, the user can convert directly from the portal the ad hoc work into a case type work class.

My Events

This tab (Data-Portal.pyCMEvents harness) contains:

An Event Subscriptions button ( ) in the left area.

• A case SLA calendar in the center area.

Case SLA Calendar — Displays case goals and deadlines based upon work item SLA values. Goals appear in orange; deadlines in red.

The user can:

View the dates by day, week, or month (default).

• Click a goal or deadline icon in the calendar to open the item.

The calendar is configured as a gadget located in the pyCMEvents section named pxCalendarViewGadget, which you can customize.
 
Event Subscriptions button — Define business events that will trigger system actions such as notifying subscribers, calling an activity, or starting a flow. The events and conditions are defined in a work item.

For example, the user could create a subscription defined as follows:

Events — A loan is resolved and the loan amount is more than

$50,000.
• Actions — The system sends an email notification to the loan department manager, and starts a process in the marketing department for setting up the customer as a gold-level account .

To define the events and related actions for a subscription, the user clicks the Event Subscriptions button to open the Event Definitions tab.
The user clicks New to open the New work item form and enters the information.

When the user clicks OK, the event definition is created and appears in the Events Definitions tab.

My Reports

This tab (Data-Portal.pyCMReports harness) displays the standard Report Browser gadget, which lets the user:

Browse and search for available existing reports.

• Create new reports and modify copies of existing reports.
• Use a library of SQL functions to build powerful expressions to return exactly the data the report needs.
• Share report shortcuts with colleagues, and use shortcuts they provide.
• Re-organize reports within defined categories.
• Run reports.
• Export reports to spreadsheets or as PDF files

Clicking an item in the list opens the report in the Report Viewer.


The user can create personal reports clicking the New Report button, which opens the Create New Report dialog.

The user opens the new report in the Report Viewer to configure it. The report can then be copied into Shared or Standard Reports categories.

Case Management in Pega

What is Case Management?

Case Management facilitates casework, guiding caseworkers to the information most relevant to their roles in the case. Caseworkers are able to collaborate, keeping abreast of the work that colleagues have done on cases via personalized event notifications.

Managing cases with Case Management increases efficiency, consistency, and visibility of case processes, which decreases costs and improves quality. Accordingly, Case Management supports the way that caseworkers work with case timelines and relevant context.
Case Management features embrace the dynamic, ad hoc, collaborative, and highly contextual nature of cases. Contextual, rules-based processing ensures that the most appropriate policies and procedures are selected for each case. This increases work automation and routing, in turn reducing the number of manual exceptions. Features include:
Rules-based contextual processing to increase automation

• Document support – add, check out, modify, and collaborate
• The ability to create ad hoc work that adds or changes the expected process based on unanticipated business events or requirements
• A facility that allows caseworkers to incorporate ad hoc work back into the process
• A graphical Case Manager portal that:
  • Provides a large array of tools and context required to efficiently manage numerous cases and their assignments
  • Gives multiple views of caseload levels and work rates in that help caseworkers understand priorities and give managers insight into performance
  • Lets caseworkers share documents and collaborate on related cases and processes
• User forms that enable caseworkers manage multiple case and subcase assignments, add new cases, or start supporting processes

Key features and attributes of Case Management

Three key feature areas of PRPC Case Management are: case design, "design-by-doing" features, and a Case Manager portal. Case design allows users to easily create a rich hierarchy of case types, associated content types and roles. PRPC Case Management also supports the dynamic and ad hoc addition of processes and cases, and "design-by-doing" allows users with permissions to capture best practices by incorporating ad hoc work back into the case design through the use of case templates.

Case Management offers:
 Dynamic & Ad Hoc Case Handling

• • Contextual processing of case is based on type, product, geography, subject, and time frame
  • Ad hoc addition and modification of processes, subcases, tasks and content to the case
• Visible, actionable, and auditable actions
  • Audit trail logs all system and user actions
  • Records the specific policy applied at every step
  • Operator-specific graphical dashboard
  • Extensive standard reports
  • Create custom reports via reporting wizard, exporting to Microsoft Excel for further analysis
• Collaborative Case Management
  • Caseworkers are informed of the status of work that colleagues are doing on cases
  • Multiple caseworkers can work simultaneously on a case without redundancy or conflicts
  • Web 2.0 collaboration is supported through collaboration portals, blogs, and wikis
  • Web access allows third-party users to collaborate on cases
  • Caseworkers in a Federated Case Management system can create and work on cases processed in another PRPC system

Case Lifecycle Management

With the Pega 7 Case Designer, you design your application by describing the stages within a case type, then define the steps or processes that happen in each stage. This provides an easy way to capture objectives in a single view that all parties, from application designers to executives to end users, can use to examine to understand how a particular case type works and progresses.

The user experience

The powerful, intuitive case management user interface provides managers and caseworkers with the features they need to ensure maximum productivity.

 The Case Manager portal provides a dashboard that enables users to:

Create, view, and work on cases

• Display unresolved cases, their subcases, and a case's open assignments
• Display associated content, users, roles, and subjects
• Monitor group status, goals, and deadlines
• Generate work management reports
• User forms provide:
  
  • Access to timelines, content, correspondence, and the status of work done on the case by other parties
  • A navigation tree enabling users to review related subcases and open their assignments
  • An Add Work menu that lets users start processes that support the case and create new cases
  • Navigation links enabling the user to open parent user forms
  • Sections for viewing parties related to the case, and for viewing and adding attachments
  • Access to Pega Pulse social activity stream that facilitates collaboration and conversation among application developers and users

  Cases Explorer

  The Cases Explorer provides a tree hierarchy for constructing and restructuring parent and child case type relationships. Your configuration dictates how cases are created and processes are started. You select a case type to view and define its configuration on a Case Designer landing page.
  

  Case Designer

  The Case Designer is organized into three tabs:
  
  • Details – enables you to define supporting processes, data propagation, service levels, subcase instantiation behavior, email notifications, and other actions.
  • Stages & Processes – displays the stages and steps that define the case type's overall process. You can access the Process Outline view from this tab, which enables you to use Process Modeler to define step processes within the context of a stage.
  • Specifications – allows you to view, create, or update a case type's specifications.

  • Case Management Gallery

    The Case Management Gallery provides a working example of a case management application. You can explore the application's structure and copy its components and rules into your own application for customization. Also included are descriptions and links to more than 60 standard flows, flow actions, and sections that are commonly used in case management designs.

  • Federated Case Management

    The Federated Case Management (FCM) product enables you to connect PRPC applications. Users logged on to a PRPC 6.3+ or PRPC 7.1+ application to create, display, update, and resolve cases in PRPC 6.3+ or PRPC 7.1+ applications hosted on other systems from within their current application portal. Each local application processes and maintains its own cases and data, and publishes data to a centralized database, the Federated Case Management Repository (FCMR.

  • Federated Case Management

    Federated Case Management (FCM) facilities enable users logged onto a PRPC 6.3+ or PRPC 7.1 application to create, display, update and resolve cases in PRPC 6.3+ or PRPC 7.1 applications hosted on other systems, from within their current application portal. Consolidated views of cases and assignments can be viewed from within any application portal in a federation. These views are enabled by the new FCM repository (FCMR), a central database to which applications in a federation publish case and assignment data.
    Sample configurations for FCM include:
    

    1. A front-end call-center application such as Pega Customer Process Manager for Financial Services (CPM-FS), federated with financial service backend systems like Pega Service Case Manager (SCM-FS) and SmartDispute.
        
    2. A distributed application, in which multiple data centers in different locations are running the same PRPC application(s) against different production databases.

     

    Key Features

    • The Federated Case Management Repository (FCMR) contains class tables for federated versions of key PRPC classes, for example, Work-Federated and Assign-Worklist-Federated. Instances of the federated classes serve as lightweight pointers to cases residing in a federation’s local application databases.
    • The federated worklist view presents workers with a consolidated list of assignments from the applications in a federation. It also provides a federated Get Next Work gadget, and the ability to create new cases of any type within the federation. This view is easily customized to include different data.
    • The federated case list view provides a consolidated list of all cases in a federation, including those currently assigned, resolved, etc. This view enables users to see a 360-degree view of all cases across a federation, filtered and sorted by customer, product, location, or any basis desired. This view

  • Important terminology

    Case: Top-level case under which all other elements are nested including subcases, processes, and content/attachments.
    • Case Type: Define the unique processing behavior and content of a case. Most case management applications handle between a few and several case types.
    • Content: Structured or unstructured documents containing information relevant to the case.
    • Dependency: A dependency indicates that different elements of a case have some association or reliance on another case in order to be created or completed.
    • Process: The entity that contains the rules and order of completion for the nested items within a given case.
    • Stage: In a Case Lifecycle Management application, a stage is a first level of organizing the tasks required to complete work associated with a case. For example, you may use checklist to capture the large, and then small, tasks needed to complete a job or project. That checklist is similar to a stage.
    • Step: Represents a task that is completed in a stage. A step can range in scope from a single assignment to a complex, multi-step process.
    • Subcase: A case that is nested under a top-level case. The subcase represents work that must be completed to resolve the case. Subcases may also be parents to other subcases.
    • Subject: The principal focus of a case. There may also be related subjects. Related subjects might be relatives, cohabiters, or related objects such as buildings, products, etc.