| java.lang.Object org.kuali.core.rules.PreRulesContinuationBase
All known Subclasses: org.kuali.module.financial.rules.DisbursementVoucherDocumentPreRules, org.kuali.module.chart.rules.MaintenancePreRulesBase, org.kuali.module.purap.rules.AccountsPayableDocumentPreRulesBase, org.kuali.module.financial.rules.BudgetAdjustmentDocumentPreRules, org.kuali.module.kra.budget.rules.budget.BudgetDocumentPreRules, org.kuali.module.financial.rules.PayeeDocumentPreRules, org.kuali.module.chart.rules.ObjectCodePreRules, org.kuali.module.purap.rules.PurchaseOrderDocumentPreRules, org.kuali.core.rules.UniversalUserPreRules,
PreRulesContinuationBase | abstract public class PreRulesContinuationBase implements PreRulesCheck(Code) | | This class simplifies requesting clarifying user input prior to applying business rules. It mostly shields the classes that
extend it from being aware of the web layer, even though the input is collected via a series of one or more request/response
cycles.
Beware: method calls with side-effects will have unusual results. While it looks like the doRules method is executed
sequentially, in fact, it is more of a geometric series: if n questions are asked, then the code up to and including the first
question is executed n times, the second n-1 times, ..., the last question only one time.
|
Inner Class :public class ContextSession | |
LOG | protected static org.apache.log4j.Logger LOG(Code) | | |
session | ContextSession session(Code) | | |
PreRulesContinuationBase | public PreRulesContinuationBase()(Code) | | |
abortRulesCheck | public void abortRulesCheck()(Code) | | This bounces the user back to the document as if they had never tried to routed it. (Business rules are not invoked.)
|
askOrAnalyzeYesNoQuestion | public boolean askOrAnalyzeYesNoQuestion(String id, String text)(Code) | | This method poses a Y/N question to the user.
Code that invokes this method will behave a bit strangely, so you should try to keep it as simple as possible.
Parameters: id - Parameters: text - |
|
|