Legacy Requirements in New Portal

Just to clarify: legacy requirements will be pulled into the new portal through a program workflow? So new requirement forms are NOT necessary for legacy requests with legacy requirements?

Comments

  • Just in case anyone else was confused since there was discussion of a migration of legacy requirements to new portal. This is not the case. Everything needs to be re-created in new portal.

    Per BB: You cannot use "legacy" forms in the new portal. Those will need to be recreated as either a Progress Report, Grant Agreement or Additional Documentation form in the new portal, and then those new forms need to be added to a given workflow before you can publish them out.

  • Hey @Arancha Lattanzio - thanks for bringing this up! Since it seems like you've gotten more info/understand this better than me… Basically any requirements published to but not yet completed on the legacy portal will need to be republished to the new portal?

    So essentially I could/should run a report for any requirements not marked done and go through each record and manually delete from web, and then publish to the new portal?

  • @Irene Tai

    Hi Irene, here are two resources for you to follow the step by step on legacy requirements. You are correct, but you can do a batch based on “received date is missing” and Form ID “is more than 35000”.

    Publish requirement form

    Blackbaud University