Write local data into table

Question

Hi Community,I need some help with my requirement  like below shown in the image we have scenarios - 1,2 etc and each scenario have some plan associated and for different plans different services. It's connected in that way. In that for a particular services with example here billcode as sc112 i need to replace it with a link . Basically think services are shown in grid fetched from reference table which will have plan id , service id connected and created for request level. So in different plans same services can be available. As mentioned for a particular billcode service i have show fee details available based on plan id it can be fetched. After request submission when next task created that fee details should be editable. So this is my requirement .But i am not able to find a logic for that, diffrent plan can have different fee details so in each service grid associated with plan will have different fee details. Anyone can help me? How can I save them into table? My overall request creation process with interface is complex, using 2 user input tasks inside a pm 1st task will have some section with plan and client and scenario details then those data will be used in the next user input task which have the services section

harshas2775 · Answer

You need to set a solid data structure first before building the grid and all!
Build reference tables first with the static data your app needs. Like services should have a reference/ look up table having unique service id and services.

then plan table should have plan related details.

The main table , scenario, should have scenario details.

Another table should be there which stores scenario id, plan ids and services ids using foreign key references as they relate. If you use records then consider setting relationships.

Taking this general idea build your Interface. For a scenario get the plans and for plans get the services.

It might seem pretty complex but using variables and process models you can pass data between interfaces (tasks). So start with tables then start designing your interface. Given my limited understanding of your use case you might need to tweak the data structure so adjust as needed and come back if you face challenges.

Sign up

Login with SSO

Login to the community

Login with SSO