Understanding Rules in PRPC

RuleSet

As a container for components of your application, a RuleSet stores a related group of business rules. It’s what you deploy in your production environment or ship to a customer. RuleSets provide security, version control, and the ability to deploy your application in (or move it to) a different Process Commander environment. You must create a RuleSet before you can build an application.

• Rule-RuleSet-Name – Which defines the RuleSet name and other characteristics
• Rule-RuleSet-Version , which defines the RuleSet Version.

Prerequisite:
When you create a new RuleSet, you can choose to specify an existing RuleSet as its parent or Prerequisite. This designation establishes a rule resolution relationship between it and your RuleSet, which can then inherit and extend existing features and characteristics.In most cases, you should specify Pega-ProCom as a prerequisite fro new RuleSets. This Process Commander RuleSet contains the standard work management capabilities that you use as building blocks for your applications.

Using the checkout feature for version management:
You also choose whether a new RuleSet should enforce version management capabilities for rule changes. This feature protects rules against simultaneous changes and conflicts by requiring you to check out a rule before changing it. Checking out a rule locks it against other changes. Creates a local RuleSet for your personal use, and copies the rule into your personal RuleSet. It also maintains a change history based on information provided when you check the rule back in.
Tip: To cancel a checkout request and unlock the rule without changing it, simply delete the rule instance in your Personal RuleSet.

What is a Class?

Classes are the foundation of any object-oriented programming (OOP) methodology. Both Process Commander classes and traditional Java classes share the following OOP characteristics:
■ You can create a hierarchy of classes. You can get a huge head start on creating an application by subclassing an existing class.
■ Subclasses inherit “methods” and “data” from their superclasses.
■ When you instantiate a subclass, the “constructors” of all its superclasses are automatically called.
■ You can create abstract or concrete classes.
■ A class can inherit from two different parent classes.

What Is the Process Commander URL?

http://rulesnt/pr3web/PRServlet

where rulesnt Network host name for the Process Commander Server(rulesnt is just an example)
pr3web Directory where the Process Commander Servlet is located(set to this default value during installation)
PRServlet Name of the Process Commander Servlet to run(Case-Sensitive)

This URL provides access to the Process Commander server, so it’s the same for all users. Each user has a profile, which is defined in the operator ID. It controls your Process Commander experience, including the home page you see when you log in, and the applications and features you can access.

An overview on Different Kinds of User in Process Commander

Make sure you understand the Standard Process Commander job functions
• Business User - A Person who uses the application you build to receive, process and resolve work
• Business Manager – A Person who uses the application you build to monitor/ approve work performance and quality for one or more groups of business user.
• Developers and Implementers - Three types of people who build and evolve Process Commander applications
Process architect - a business user or business analyst who defines and maintains business rules, Service levels, and flows or Processes
System architect - an application developer who creates the class structure fro your work with supporting automation capabilities and implements interfaces with external systems.
System administrator – a systems engineer who is responsible for installation and setup, security and other operational functions

Advantages of Process commander

• Process modeling :Thin-client development environment geared for business users
• Process brokering:One-click integration with MQSeries, CORBA, SOAP, etc.
• Process Management:User modification of rules ,Service level agreement (SLA) and work urgency management
• Process Monitoring:Throughput reporting,Performance Analyzer and Tracer diagnostic tools
• Enterprise Rules Engine:Inherited, object-oriented rulebase,RuleSet and version management
• Cross-platform:Portability across Unix, Windows 2000, zOS
• Business Integration:Multiple engines sharing a common rulebase,ASP-capable (application service provider) architecture,Directed external access

PegaRULES – An Overview

PegaRules Process commander is a revolutionary solution for building systems that automate work. PegaSystems solves the enterprise work automation problems by providing an architecture that separates the strategic business logic from both the application and the underlying operating system. Just as business data (i.e., Customer, transaction history and accounting data) belongs in its own database, rules regarding business practices belong in a distinct business rules database (or Rulebase). Storing rules in a visible user- configurable rulebase provides business users with control of their business practices and processes.

About Pegasystems

Pegasystems Inc. (Nasdaq: PEGA) provides software to automate complex, changing business processes. Pegasystems, through its unified process and rules technology, gives business people and IT departments the ability to use best processes across the enterprise and outperform their competition.
Our new class of Business Process Management (BPM) technology makes customers' enterprise systems easy to use and easy to change. By replacing policy manuals, system specifications and lines of manual coding with dynamically responsive updates, Pegasystems powers the world's most sophisticated organizations to "build for change".
Pegasystems award-winning, standards-based BPM suite is complemented with best-practice solution frameworks to help leaders in the financial services, insurance, healthcare, manufacturing and government markets drive growth and productivity.
Headquartered in Cambridge, Mass., Pegasystems has regional offices in North America, Europe and the Pacific Rim.