1 / 22

Comprehensive Guide to Kuali's Qualifier Resolver and Document Management Systems

This document outlines the capabilities of the Qualifier Resolver in Kuali's workflow engine. It explains how the resolver identifies qualified roles associated with documents through a systematic approach using Route Context for information retrieval. Additionally, it covers enhancements in application tooling for documentation and configuration management. Various dictionaries are discussed, including service and orchestration dictionaries, facilitating improved integration and usability of Kuali's services within document content and application development.

keiko-suarez
Télécharger la présentation

Comprehensive Guide to Kuali's Qualifier Resolver and Document Management Systems

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. KEW Definitions

  2. DocumentType XML

  3. Document Content <documentContent> <applicationContent> <cluProposalDocInfo> <cluId>0ed64e1f-9d24-4b10-b21a-e366fc77cc9d</cluId> <orgId>69</orgId> <proposalId>44edf1d5-88d0-46d5-b51b-c6e833029ced</proposalId> </cluProposalDocInfo> </applicationContent> </documentContent>

  4. Qualifier Resolver import org.kuali.rice.kew.engine.RouteContext; import org.kuali.rice.kim.bo.types.dto.AttributeSet; /** * A QualifierResolver is responsible for resolving qualifiers that might be used * to identify a Qualified Role from a Document. Information about the Document * can be obtained from the RouteContext. * * @author Kuali Rice Team (rice.collab@kuali.org) * */ public interface QualifierResolver { public List<AttributeSet> resolve(RouteContext context); }

  5. Post Processor

  6. Dictionaries • Service Dictionary, Data Dictionary, DTO Dictionary • Search Dictionary • Orchestration Dictionary, DOL Dictionary • Search Orchestration Dictionary • Not just lookup meta data • Most likely part of regular Search Dictionary • Application Dictionary?

  7. Service Dictionary Configuration • Override value settings • Add constraints • Remove constraints • Override constraints • Override global constraints? • We don’t think this is likely

  8. Spring Config Files • Inheritance from parent bean • Last bean defined with same ID wins • Include files from classpath • Could we include from url? • Would we want to include from url? • Parent bean pattern for overrides

  9. Inheritance

  10. Parent Bean Pattern

  11. Parent Bean Patter

  12. Tooling • Could use standard XML tools • Excel generation • This needs updated output for configurability • Application based tooling • Implementing institution could contribute • Recently added functionality that reads java service DTO’s and creates dictionary stub

  13. We Have Schema Posted

  14. Orchestration Dictionary • Is this orchestration/transformation only or should it control UI? • Needs linkage to Service Dictionary • Remove redundant constraints • Provide global config

  15. Application Dictionary Could: • Configure document content • Configure document type • Configure UI • Tie screen to orchestration dictionary/object

  16. Transactions • Solution must implement ws-coordination spec and jta spec (in order to be swappable/purchaseable) • Attempt to create new service methods to reduce numbers of transactions • Currently stuck deploying all services and UI as single application • Possibly attempt to write transactions based on ws spec • Compensation is as much or more work than writing atomic

  17. Transactions In Glassfish • Dropping KS on Glassfish does not get transaction support • Must integrate with some or all of containers implementations of • JTA • JPA • JAX-WS • JNDI Datasource • KSB integration with Metro on Glassfish

  18. Dynamic Attributes • Supported via simple configuration at • Service level • Service dictionary • Pickers • DOL • Must create Orchestration dictionary • Must modify DOL Assemblers • Must modify UI via deferred binding • Need to build an “LU/Course” example into codebase or deployment lab

  19. Authorization Layers • Service Layer • KS application clients and external clients • Lowest level of row/field authorization • Orchestration Layer • May need access to row/fields user can’t access • Needs to respect service layer authZ • Application Layer • Access to particular application • View a specific section • Data must be filtered before this layer since it runs on the browser

  20. Field level AuthZ and Masking • Permissions are positive • Configurations are negative • Assume all fields are editable unless configured otherwise in Dictionary (DOL or Service) • Permissions checked to override configuration

  21. Application Authorization AuthZ Filter DOL Service Layer 4 3 GWT Client 2 1 5 6 7 KIM Permission Service

  22. AuthN Diagram • https://test.kuali.org/confluence/display/KULSTG/KS+Authentication

More Related