Having a global object repository that is usable across all scripts, and a local object repository that is usable across scripts in the same folder

[kensoh]

In current version of TagUI, repository for storing commonly used objects or definitions only exist locally per automation flow. However, there are situations where users can have multiple automation flows that want to make use of a common repository definition.

In current implementation, that would involve duplicating a repository file for each automation script, and adding definitions local for each script. For this use scenario, it is a hassle for maintenance.

This issue aims to add support for letting users create a tagui_global.csv file in tagui/src folder, which they can define global repository definitions for use in their automation scripts. And tagui_global.csv persists with newer TagUI releases as there isn't a tagui_global.csv file as part of the repo.

[kensoh]

Above commit handles

• using global repository with a local flow-specific repository file. local definitions will take precedence over global definitions

• using global repository with a flow with datatable having multiple records for iterations

• a possible adjacent improvement for consideration related to this issue is handling local datatable files which only the 2nd column is filled in for some rows with the purpose of being used as repository definition role

[kensoh]

This feature is now usable from the cutting edge version. Having a tagui_global.csv in the tagui/src folder will include the object definitions in this global repository file and make them available for all automation flows. When there is the same definitions, flow-specific repository definitions take precedence over the global definitions. This global repo file works with a flow has datatable.

[kensoh]

A possible adjacent improvement for consideration related to this issue is handling local datatable files which only the 2nd column is filled in for some rows with the purpose of being used as repository definition role.

[kensoh]

For local datatable files with only 2nd column filled, if blank columns are padded with column 1 data, it is not deterministic. An elegant implementation is extend the idea of global repository tagui_global.csv which is accessible from all automation flows.

By creating local repository file tagui_local.csv. All automation flows in the same folder as the tagui_local.csv will be able to access the definitions defined in the local repository file. Precedence in event of conflicting same definitions is -> flow-specific repository, followed by local repository, followed by global repository. Above commit implements this feature.

Similar to tagui_global.csv, the file tagui_local.csv is not something that is part of TagUI codebase, thus it will persist with new releases and users' modifications can be retained.

This feature is now usable from cutting edge version.