TOD AIB - Table 7 - Columns 8 and 9 + formulas
Columns 8 and 9 are editable in the following cases:
System path
MNT
TOD EMFAF - Table 9 - Columns 11, 12, 13 and 14
Columns 11, 12, 13 and 14 are editable in the following cases:
TOD EMFAF - Table 5 - Columns 11 and 12
Columns 11 and 12 are editable in the following cases:
TOD IJG - Table 10 - Columns 10 and 11 + Formulas
Columns 10 and 11 and their gender breakdown are editable and mandatory in the following cases:
Modified on
2 years 1 month ago
TOD IJG - Table 6 - Columns 9 and 10 + Formulas
Columns 9 and 10 and their gender breakdown are editable and mandatory/optional in the following cases:
Modified on
2 years 1 month ago
TOD IJG - Table 9 - Columns 11, 12, 13 and 14 + Formulas
Columns 11, 12, 13 and 14 are editable in the following cases:
Use case non-JTF |
Modified on
2 years 1 month ago
TOD IJG - Table 5 - Columns 11 and 12 + Formulas
Columns 11 and 12 are editable in the following cases:
Use case non-JTF |
Modified on
2 years 1 month ago
TOD ETC - Table 9 - Columns 11, 12, 13 and 14 + Formulas
Columns 11, 12, 13 and 14 are editable in the following cases:
TOD ETC - Table 5 - Columns 11 and 12 + Formulas
Columns 11 and 12 are editable in the following cases:
Modified on
2 years 6 months ago
Standalone Documents - Why does SFC only allow the creator to send a document?
Documents and more specifically the Standalone/Referring documents don't have a workflow and without transaction between MS nodes, because this is more flexible and more convenient for users and best reflects how document transmission in most organizations work.
The only type of status is sent or not sent, so a creator cannot indicate that he finished editing the document, that he uploaded all the necessary files, and that the document is ready to be sent. If we would allow someone other than the creator to send, this person could send incomplete documents.