Hardcoded Fields in ISLG
Hi
Morgan
Harsh
Here is a link to a spreadsheet which contains a list of all the hardcoded fields in ISLG:
https://docs.google.com/spreadsheets/d/1PZh32E5n1wKbPuL_SxWIVzzmRsUVjs1bzjvbUEkxaQ4/edit?usp=sharing.
I have included all the columns that exist in the ISLG Meta Data Field map, however I only filled out information that was written in the target process cards, and that reflect the current implementation. There are also several cells that are highlighted yellow, this is because I could not verify the current implementation of them (for example whether they are required or not) without creating test data in the application.
I will go ahead and audit the subscriber side to be sure that all of the fields that should be hardcoded are on this spreadsheet, and update accordingly.
Thanks,
Naomi
Morgan
Harsh
Here is a link to a spreadsheet which contains a list of all the hardcoded fields in ISLG:
https://docs.google.com/spreadsheets/d/1PZh32E5n1wKbPuL_SxWIVzzmRsUVjs1bzjvbUEkxaQ4/edit?usp=sharing.
I have included all the columns that exist in the ISLG Meta Data Field map, however I only filled out information that was written in the target process cards, and that reflect the current implementation. There are also several cells that are highlighted yellow, this is because I could not verify the current implementation of them (for example whether they are required or not) without creating test data in the application.
I will go ahead and audit the subscriber side to be sure that all of the fields that should be hardcoded are on this spreadsheet, and update accordingly.
Thanks,
Naomi
Thanks for the above. This really helps make sense of things. It looks like large parts of the forms are now hard coded fields, which increases the importance of making the hard coded fields visible and capable of being reordered within the meta-field management page. For example, further to the video below, there is an issue with one of the hard coded fields within the Disputes form, and this could be quickly resolved by admin user if we were able to move the field into the applicable Annulment Committee field set.
Thanks,
Morgan
To consolidate everything into one place, I've taken your spreadsheet and added as a tab to the ISLG Meta Field Map and then added a column in each master list to indicate whether each field is hard coded are not in the main tab: https://docs.google.com/spreadsheets/d/1Ho_yBR8gfCIqivmvkPy_hISkDGozdWsXxn46ImeQ-V4/edit#gid=1780667146. If further edits to the table of hard coded fields are required, please make them in the Hard Coded Fields tab, and then it should automatically update the main tab.
Thanks,
Morgan
I observed that so many fields are not considered as hard coded field which we discussed during subscription story discussion.
For Ex.
Dispute
-
Non-Investment
- Lanaguage
Treaties
- Date of conclusion
- Date of Force
- Language
Arbitration
- Language
These are few examples which i observed. please make sure we considered all hard coded fields which we discussed.
I've gone through the Subscriber side, and added any fields that were missed to the 'Hardcoded Fields List' in the Meta Data spreadsheet. You will see these highlighted in green.
For those that require stories in ISLG Admin to implement this, I will create those, and link them back to this thread.
Edit: Here is the link to the target process card relating to additional hardcoded fields: https://industrialagency.tpondemand.com/restui/board.aspx?#page=board/5389754907359543952&appConfig=eyJhY2lkIjoiNkIwOEFBRTU1NUY0ODJDNDU1NDA1NzJFQkE5N0JGQjkifQ==&boardPopup=feature/1829/silent
Thanks,
Naomi
Thanks,
Morgan