Work the partnerships, compliance and documents screens

Three tabs on a program. Each offers more than it does, and one of them offers a compliance verdict it has not calculated. This page says what each can actually do and what to use instead.

Who can do this

• Site director
• Organisation admin
• Super admin

management

All three tabs are inside a program's own layout, so a regional director sees a failure message on each, and a staff member is excluded by the module's own setting.

Partnerships

What works

You can create a partnership between this program and an existing partner organisation, and you can see the list with each partner's name, role, start date and counts of agreements and contributions.

1. Click New Partnership.
2. Choose a Partner Organization from the dropdown.
3. Role, free text, for example Content Provider.
4. Start Date and Notes, optional.
5. Click Create.

If the partner dropdown is empty, nothing on this tab will work, and there is no way to fix it from PTRS

The dropdown is filled from PTRS's list of partner organisations. Nothing in PTRS creates one; that action has a client function and a control ready to call it, and nothing anywhere in the product actually calls it.

If no partner exists, the dropdown shows only a prompt to select one, and clicking Create does nothing at all: PTRS stops before sending anything, so there is no request, no error and no message.

What to do: a partner organisation has to be added by someone with database or direct access before this tab can be used. There is no screen for it, in Programs or anywhere else.

What this tab cannot do

Partnership limitations

• A partnership is always Proposed. The dialog sets that stage and offers no control to change it, and there is no action that would correct a partnership. Active, On Hold, Completed and Terminated are all unreachable, so the Active counter is permanently zero.
• No end date. The field exists on PTRS's side; the dialog has no input for it. Every partnership reads "Ongoing".
• No agreements. Both actions behind agreements are reachable from no screen. The Agreements counter is permanently zero.
• No contributions. Both contribution actions are reachable from no screen. The Contributions counter is permanently zero, and even when rows exist nothing sums their value.
• No delete, for a partnership or a partner.

Two labels on this screen

The Total Partners card counts partnerships, not partner organisations.

The Role field is free text on PTRS's side, and the screen holds a label for six specific role names. Since the input is free text and the placeholder suggests "Content Provider" with a space, what you type is almost always shown back exactly as typed, and that label is rarely consulted. Nothing breaks either way.

Compliance

This tab shows every program as 0% Compliant, and it has not checked anything

This screen does not connect to PTRS at all. Its requirements list is a fixed, empty value built into the screen, and it discards the program it is looking at.

Because the list is empty, the score is zero, and because the badge is red below 60, the screen prints a red 0% Compliant under the heading "Track DELACARE, OCCL, and federal compliance for this program".

Nothing is wrong with your program. The screen has never asked PTRS anything. It looks identical for a program with every requirement met and for one with none, in every organisation.

Both actions behind it, reading and setting a program's compliance requirements, work correctly and neither is reachable from any screen.

There are no controls on this tab. There is no Add Requirement button, because there is nothing to add it to.

What to use instead. Program-level compliance requirements cannot be recorded in PTRS today. The compliance surfaces that do hold real data are:

• Centers, licensing and inspections, the OCCL licence and inspection records for the site.
• Compliance, the organisation-level module, whose own caveats are on its landing page.
• Staff credentials, the credential expiry tracking that does run.

If this tab is wired up later, the shape will still not match

The screen's own local field names do not match what PTRS would actually send back, and one field the screen expects does not exist on the record at all. The colour map also keys on a category name that is not real, and has no colour for eight categories that are.

Documents

What works

You can create a document record against the program and list them. That is the whole of it.

1. Click Upload Document.
2. Title, required.
3. Document Type, see the warning below. Leave it blank.
4. Description, optional.
5. File URL, required. Type or paste a web address.
6. File Name, optional; it drives the file-type icon.
7. Click Upload.

Upload Document does not upload a file

There is no file picker on this dialog. It has two plain text boxes, File URL and File Name, and no way to actually choose a file from your computer, and no storage call anywhere in the flow.

What you are creating is a record that points at a web address you typed. Nothing checks that it resolves to anything, and PTRS does not hold the file. If you need PTRS to store a file, this is not the screen; member documents and scanned forms go through Quick Scan, which does store what it is given.

The Document Type placeholder suggests two values PTRS rejects

The placeholder reads "e.g., Policy, Compliance, Form". PTRS accepts Charter, Policy, Procedure, Report, Agreement, Certificate, License, Insurance, Budget, Grant, Evaluation and Other.

• Compliance, not a valid choice, refused.
• Form, not a valid choice, refused.
• Policy, accepted.
• policy, refused, because this match is exact, including case, unlike the budget category match next door.
• Blank, the screen substitutes Other, which is accepted.

Leave the box empty, or type one of the twelve names exactly.

What this tab cannot do

Document limitations

• No new version. The action is wired up in the screen and no control calls it. There is no New Version button.
• Version history is always empty. Two independent reasons: nothing can create a second version, and creating the document does not write the first version either, it only sets the current version number and inserts nothing into the version history. Expanding Version History always shows "No version history".
• No archive. The document's active flag has no writer after creation, so the Archived counter is permanently zero and the archived badge and dimming never render.
• No edit and no delete.

Version history would show a long code, not a name

Whoever uploaded a version is recorded as a raw sign-in account identifier, and the panel prints it where a person's name belongs. The time beside it is shown as raw, unformatted text.

Related

• Who can do what with money and governance
• What Programs can and cannot account for
• Programs troubleshooting