Added new functionality requested in issue 374. Format: "[ date [ member [1 2 3 4 ] ] ],SECTION,SECTION" is allowed, where:
- SECTION represents a section, e.g. SIM, it can also be the keyword 'Any', meaning that the changes provided in the formula (JSON string) apply to all the jobs, taking also into consideration the rules provided in the formula.
- date represents a starting date, it does not accept the keyword 'Any', although implementing that seems straightforward, but since it is not openly requested it has been ignored.
- member represents a member in the formula, e.g. fc0, it can also take the value of the keyword 'Any', meaning that the chunks provided for that member will change in every member, otherwise, only the chunks of the provided member will change.
- chunks [1 2 3 4], any number of chunks is accepted. Format "1-99" is not accepted. Keyword 'Any' can be implemented, but as with starting dates, it has been temporarily ignored.
After the changes have been performed, the system will ask the user if he wants to see an extended description of the changes, a yes no question. If 'y' a string representation of the job list dependency hierarchy including changes performed will be shown (see attached image).
It also serves as a quick debugging tool. More data can be incorporated into this representation.