Web portal application customization method and system using profiles

• US 8,397,211 B2
• Filed: 02/25/2010
• Issued: 03/12/2013
• Est. Priority Date: 11/02/2009
• Status: Active Grant

• Current Assignee: Accenture Global Services Limited (Accenture PLC)
• Original Assignee: Accenture Global Services Limited (Accenture PLC)
• Inventors: Ionfrida, Nicola, Cardinale, Paolo, Comis, Carlo
• Primary Examiner(s): KENDALL, CHUCK O
• Application Number:
  US12/712,835
• Publication Number:
  US 20110107294A1
• Time in Patent Office: 1,111 Days
• Field of Search: None
• US Class Current: 717/105
• CPC Class Codes: G06Q 30/02 Marketing; Price estimation or determination; Fundraising
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation

Abstract

Web portal application customization methods and systems using profiles allow developers to expose different functionalities and a different look and feel to users belonging to different user profiles. Specifically, the method allows a developer to define default and profile-specific transitions as well as default and profile-specific states. Upon request of a transition by a workflow engine, the system transparently provides the workflow engine with a profile-specific transition if a profile-specific transition associated with the user is available. If a profile-specific transition is not available, the system provides the application with a default transition. Likewise, the system transparently provides the application with a profile-relevant state according to the profile of the user and the availability of a profile-specific state. Accordingly, the method may implement highly customizable functionalities and look and feel effectively and cost-efficiently.

Claims

1. A method for customizing a software application, comprising:

storing in a memory a profile associated with a user;

storing in the memory a plurality of states, each state being associated with a user interface;

storing in the memory a plurality of transitions including a default transition and a profile-specific transition, each transition including a task to be performed by a workflow program;

executing with a processor the workflow program, the workflow program comprising logic that when executed causes the processor to;

identify the profile associated with the user;

display the user interface of a state of the plurality of states;

receive from the user a transition input available for the state, where the transition input is associated with a transition of the plurality of transitions;

determine whether or not a profile-specific transition associated with the received transition input which corresponds to the profile of the user exists;

if a profile-specific transition associated with the received transition input which corresponds to the profile of the user exists, retrieve the profile-specific transition associated with the received transition input as a retrieved transition;

if no profile-specific transition associated with the received transition input which corresponds to the profile of the user exists, retrieve the default transition associated with the received transition input as the retrieved transition; and

perform the task included in the retrieved transition.

2. The method for customizing the software application of claim 1,

wherein the logic to determine whether or not a profile-specific transition exists further includes logic to request a controller for the transition associated with the received transition input, where the controller searches the memory for a profile-specific transition associated with the received transition input which corresponds to the profile of the user;

wherein the logic to retrieve the profile-specific transition associated with the received transition input as the retrieved transition further includes logic to retrieve the profile-specific transition using the controller; and

wherein logic to retrieve the default transition associated with the received transition input as the retrieved transition further includes logic to retrieve the default transition using the controller.

3. The method for customizing the software application of claim 1, further including storing in the memory a plurality of templates,

wherein the logic to display the user interface of the state of the plurality of states further includes logic to retrieve from the memory a template of the plurality of templates and logic to apply the retrieved template to the user interface.

4. The method for customizing the software application of claim 3,

wherein the plurality of templates includes a default template and a profile-specific template,

wherein the logic to retrieve the template further includes logic to:

determine whether or not a profile-specific template associated with the user interface corresponding to the profile of the user exists;

if a profile-specific template associated with the user interface corresponding to the profile of the user exists, retrieve the profile-specific template as the retrieved template;

if no profile-specific template associated with the user interface corresponding to the profile of the user exists, retrieve the default template as the retrieved template.

5. The method for customizing the software application of claim 3,

wherein the template of the plurality of templates includes a default section and a profile-specific section,

wherein the logic to apply the template further comprises logic to:

apply a default section; and

if a profile-specific section corresponding to the profile of the user exists, apply the profile-specific section.

6. The method for customizing the software application of claim 1, wherein the profile-specific transition includes a profile-specific task to be performed by the workflow program.

7. The method for customizing the software application of claim 1, wherein the tasks to be performed by the workflow program includes proceeding to a next state of the plurality of states.

8. A system for customizing a software application, comprising:

a processor;

a computer readable memory coupled to the processor and storing;

a profile associated with a user;

a plurality of states, each state being associated with a user interface;

a plurality of transitions, including a default transition and a profile-specific transition, each transition including a task to be performed by a workflow program;

a workflow program, the workflow program comprising logic that when executed causes the processor to;

identify the profile associated with the user;

display the user interface of a state of the plurality of states based on the information for displaying the user interface;

receive from the user a transition input available for the state, where the transition input is associated with a transition of the plurality of transitions;

determine whether or not a profile-specific transition associated with the received transition input which corresponds to the profile of the user exists;

if a profile-specific transition associated with the received transition input which corresponds to the profile of the user exists, retrieve the profile-specific transition associated with the received transition input as the retrieved transition;

if no profile-specific transition associated with the received transition input which corresponds to the profile of the user exists, retrieve the default transition associated with the received transition input as the retrieved transition; and

perform the task included in the retrieved transition.

9. The system for customizing the software application of claim 8,

wherein the logic to determine whether or not a profile-specific transition exists further includes logic to request a controller for the transition associated with the received transition input, where the controller searches the memory for a profile-specific transition associated with the received transition input which corresponds to the profile of the user;

wherein the logic to retrieve the profile-specific transition associated with the received transition input as the retrieved transition further includes logic to retrieve the profile-specific transition using the controller; and

wherein the logic to retrieve the default transition associated with the received transition input as the retrieved transition further includes logic to retrieve the default transition using the controller.

10. The system for customizing the software application of claim 8, the memory further storing a plurality of templates,

wherein the logic to display the user interface of the state of the plurality of states further includes logic to retrieve from the memory a template of the plurality of templates and logic to apply the retrieved template to the user interface.

11. The system for customizing the software application of claim 10,

wherein the plurality of templates includes a default template and a profile-specific template,

wherein the logic to retrieve the template further includes logic to:

determine whether or not a profile-specific template associated with the user interface corresponding to the profile of the user exists;

if a profile-specific template associated with the user interface corresponding to the profile of the user exists, retrieve the profile-specific template as the retrieved template;

if no profile-specific template associated with the user interface corresponding to the profile of the user exists, retrieve the default template as the retrieved template.

12. The system for customizing the software application of claim 10,

wherein the template of the plurality of templates includes a default section and a profile-specific section,

wherein the logic to apply the template to the user interface further comprises logic to:

apply the default section; and

if the profile-specific section corresponds to the profile of the user, apply the profile-specific section.

13. The system for customizing software application of claim 8, wherein the profile-specific transition includes a profile-specific task to be performed by the workflow program.

14. The system for customizing software application of claim 8, wherein the task to be performed by the workflow program includes proceeding to a next state of the plurality of states.

15. A method for customizing a software application, comprising:

storing in a memory a profile associated with a user;

storing in the memory a sitemap resource file,

wherein the sitemap resource file includes a node representing a state of a workflow, and

wherein the node includes;

a tag identifying accessibility of a user associated with a profile to the node, and

a state information of the state represented by the node;

receiving a request from a workflow program for the state information of a state of the node;

identifying the profile associated with the user;

searching the sitemap resource file for the node representing the state included the requested state information;

identifying the tag of the node representing the state including the requested state information;

determining accessibility of the user to the requested state based on the tag of the node representing the requested state; and

if the requested state is determined to be accessible to the user, communicating the state information to the workflow program.

16. The method for customizing the software application of claim 15, wherein the sitemap resource file further includes a parent node of the node representing the state of the workflow, wherein the parent node includes a tag identifying accessibility of a user associated with a profile to the parent node,

the method further comprising:

identifying the tag of the parent node;

determining accessibility of the user to the requested state based on the tag of the parent node.

17. A system for customizing a software application, comprising:

an application component;

a resource manager in communication with the application component, the resource manager storing a plurality of resources which includes a default resource and a profile-specific resource;

a resource repository in communication with the application component and the resource manager; and

a profile manager in communication with the resource manager;

wherein the resource manager;

receives from the application component a request for a resource of the plurality of resources,

receives from the profile manager a profile information associated with a user,

determines whether or not a profile-specific resource associated with the requested resource which corresponds to the profile of the user exists in the resource repository;

if a profile-specific resource associated with the requested resource which corresponds to the profile of the user exists in the resource repository, provides the profile-specific resource associated with the requested resource which corresponds to the profile of the user to the application component as the requested resource; and

if no profile-specific resource associated with the requested resource which corresponds to the profile of the user exists, provides a default resource to the workflow engine associated with the requested resource which corresponds to the profile of the user to the application component as the requested resource.

18. The system for customizing the software application of claim 17,

wherein the resource manager comprises a controller;

wherein the plurality of resources further includes a plurality of transitions including a default transition and a profile-specific transition, each transition including a task to be performed by the application component; and

wherein the default resource and the profile-specific resource comprises a default transition and a profile-specific transition, respectively.

19. The system for customizing the software application of claim 17,

wherein the resource manager comprises a controller;

wherein the plurality of resources further includes a plurality of states including a default state and a profile-specific state, each state being associated with a user interface; and

wherein the default resource and the profile-specific resource comprises a default state and a profile-specific state, respectively.

20. The system for customizing the software application of claim 17,

wherein the resource manager comprises a template manager;

wherein the plurality of resources further includes a plurality of templates including a default template and a profile-specific template;

wherein the default resource and the profile-specific resource comprises the default template and the profile-specific template, respectively;

wherein the request from the application component for a resource of the plurality of resources comprises a request for a template of the plurality of templates; and

wherein the application component applies the requested template to a user interface.

21. The system for customizing the software application of claim 20,

wherein a template of the plurality of templates includes a default section and a profile-specific section.

22. The system for customizing the software application of claim 18, wherein the profile-specific transition includes a profile-specific task to be performed by the application component.

23. The system for customizing software application of claim 18, wherein the task to be performed by the application component includes a task to proceed from a state to a second state, wherein a state is associated with a user interface.