I have been publishing my legacy requirements to the new portal as follows: * Navigate to the Requirement * Select Requirement to be Published * Publish to the Web * Publish to a New Application * Select Requirement Form * Publish Is this correct? When I do this, I have had applicants tell me they cannot submit an application because the system tells them they have already submitted an application. My Program is set to "Always Open" What am I missing?

nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Publishing Legacy Requirements and New Application

Beth Broomall

I have been publishing my legacy requirements to the new portal as follows:

Navigate to the Requirement
Select Requirement to be Published
Publish to the Web
Publish to a New Application
Select Requirement Form
Publish

Is this correct?

When I do this, I have had applicants tell me they cannot submit an application because the system tells them they have already submitted an application. My Program is set to "Always Open" What am I missing?

Find more posts tagged with

Accepted answers

Hannah Saeger Karnei

If they can provide screenshots you want to make sure they are clicking on the requirement form within the tile, they may be mistakenly clicking on the "fake" application the system creates to link the legacy to the new portal.

All comments

Hannah Saeger Karnei

Beth Broomall

Great idea! I will have the grantee send me screen shots.

Beth Broomall

Here are samples of screen shots one of my grantees sent me. I do not know what I am doing wrong, but she cannot find the requirement and she cannot start a new application.

I am most certain I am the reason she cannot locate the requirement. Chances are I did something wrong.

As the for application form, I have not idea what is going on. Can someone help me! It seems like my long-standing grantees cannot find the application, but every new applicant can.😫

Hannah Saeger Karnei

My next check would be double checking the Applicant Account contact on the REQUEST. When publishing legacy requirements it will default to the primary contact (which for us is often not the reporting contact)! It may be you need to update there.