208
edits
Changes
Task creation rules with a file was added
<br>
<br>
<br>
<br>
==Task creation rules with a file ==
Depending on the company and its place in the hierarchy, the file uploaded by a company (FW, configurations, etc.) will have a different access range while creating tasks. Please refer to an example and rules below.
Example hierarchy of companies:
* A (parent company)
** B (child company of A)
** C (child company of A)
*** D (child-child company of C)
The following actions will be available for creating tasks:
* Any company can create a task with a file that is within the same company. For example:
** "A" company can create a task for "A" company with "A" company's file.
* Parent company can create a task for a child company with a parent company's file. For example:
** "A" company can create a task for "B" company with "A" company's file.
** "C" company can create a task for "D" company with "C" company's file.
** "A" company can create a task for "D" company with "C" company's file.
Due to logical issues that might occur, the following options won't be available for creating tasks:
* Parent company cannot create a task for itself with a child company's file. For example:
** "A" company cannot create a task for "A" company with "B" company's file.
** "C" company cannot create a task for "C" company with "D" company's file.
* Parent company cannot create a task for a child company with another child company's file. For example:
** "A" company cannot create a task for "B" company with "C" company's file.
** "A" company cannot create a task for "D" company with "B" company's file.
<br>
<br>
