Project should not close, if project task has attachment man/key milestone task is open state

[Lalith_kumar_s]

How can we prevent a project from being closed when there are open key milestone tasks or tasks with mandatory attachments that have not yet been completed?

Scenario: A project should not move to the closed status if:

• Any key milestone task is still in an Open state.
• Any task with a mandatory attachment requirement is incomplete or the required attachment has not been uploaded.

Has anyone implemented a validation or business rule to enforce this behavior? What is the recommended approach?

Or, as a requirement statement:

Requirement: The system must prevent project foreclosure when at least one key milestone task remains open or when a task with mandatory attachments is not completed with the required attachments.

[pavani_paluri]

Hi @Lalith_kumar_s 

Yes, this can be enforced through a Before Update Business Rule on the Project table.

When someone tries to move a project to Closed, the rule can validate all related project tasks and prevent the closure if:

• Any Key Milestone task is still in an Open state.
• Any task marked as requiring a mandatory attachment is not completed.
• A required attachment has not been uploaded for the task.

If any of these conditions are met, you can display an error message such as:

"Project cannot be closed because there are open key milestone tasks or mandatory attachments are missing."

This approach is generally preferred because it enforces the validation regardless of how the project is updated, whether through the UI, Flow Designer, imports, or APIs.

Another option is to use a Flow or Project State Model validation, but a server-side Business Rule provides the strongest enforcement and is usually the most reliable solution for this type of requirement.

Mark it helpful if this helps you to understand. Accept solution if this give you the answer you're looking for

Kind Regards,

Pavani P

[Its_Azar]

Hi there @Lalith_kumar_s 

A Before Update Business Rule on the Project table is enough for this. When the project state changes to Closed, validate that:

• No key milestone tasks are still open.
• All tasks requiring mandatory attachments have the required attachments uploaded.