Last post Oct 15, 2016 04:39 AM by rajaramanatwork
Oct 15, 2016 04:39 AM|rajaramanatwork|LINK
My effort is to plan to build a web based UI Application that would be a host of
a) Workflows , Workflow Definitions, Workflow Instances
b) Workflow would be a custom database driven implementation instead of standard tools like K2.NET, Windows Workflow , etc.
c) Dashboard Views /Custom Views
Idea is to to give a very singular , integrated UI Experience instead of hopping websites for viewing enterprise data something close to a Portal. Using Existing Portal Software is not a choice and we have been asked to build on ASP.NET MVC 5
Regarding Workflow, there would be Tasks which can be as simple as a button. For the Task to be performed, users might have different views that would be configurable. Each Task can execute in 2 contexts
1) Legacy App Context : wherein we will redirect to an external link (for legacy Websites, where the task be performed , since these are existing apps in the enterprise and the cost to change is not something we will get approval.
2) New App Context /Tasks- we can host pluggable views like partial ASP.NET MVC Views in one Single .NET UI Project , since these task views are yet to be created.
Question is over option #2 ( New App Tasks ) , since App's can be across many businesses in the enterprise.
Regarding #2, i propose the following choices
1) There would be Application specific WebAPI's , and app Specific Task Views that are all in one UI Project ( that can consome app Specific webAPI's), so that we can better control view injections, navigation and give a single page app experience
2) Host each of these Tasks Views as a separate Web Application ( like RCQ, RLU) with its own App Pools. This would mean hopping multiple websites for performing one workflow.
Which do you think will give a
1) Better UI Experience 2) Will endore UX Design Principles , etc.