“questionnaireRegionStatus”: [ { “questionnaireId”: 216, “regionCode”: 1, “status”:…
- User
“questionnaireRegionStatus”: [ { “questionnaireId”: 216, “regionCode”: 1, “status”: “PENDING” }, { “questionnaireId”: 216, “regionCode”: 2, “status”: “PENDING” }, { “questionnaireId”: 216, “regionCode”: 3, “status”: “PENDING” }, { “questionnaireId”: 216, “regionCode”: 4, “status”: “PENDING” }, the above is the a sample response for a user role director when fetching questionnaires. A director can doesnt have an associated regionCode but sees all other regions data. And below is the sample responce for a statstician who only see questionnaires associated with their region code “parentQuestionnaireId”: 183, “updatedAt”: “2023-06-07T11:49:13.092Z”, “createdAt”: “2023-06-07T11:49:13.083Z”, “questionnaireRegionStatus”: [ { “questionnaireId”: 216, “regionCode”: 2, “status”: “PENDING” } ], now based on this i want to modify my render function so that it accomadates for both situations. Here are my render functions { title: “Status”, dataIndex: “status”, width: “15%”, key: “status”, render: (_, data) => { if (isUserDetailsSuccess) { const status = getQuestionnaireStatusData(data, userDetails.data.regionCode); return renderQuestionnaireStatus(status); } else { return renderQuestionnaireStatus(‘-’); }
}, }, const getQuestionnaireStatusData = (data, userRegionCode) => { let status = ‘’; // console.log('data: ', data.questionnaireRegionStatus); if (data.questionnaireRegionStatus.length !== 0) { // console.log('questionnaireRegionStatus: ', data.questionnaireRegionStatus); // console.log('userDetails region: ', userDetails.data.regionCode);
const qRegStatus = data.questionnaireRegionStatus.find(qRegStatus => qRegStatus?.regionCode === userRegionCode); if (qRegStatus !== undefined) { // console.log('qRegStatus: ', qRegStatus); status = qRegStatus.status; }
}
return status; } items={ [ { key: ‘1’, label: ‘View Cleaned’, disabled: isUserDetailsSuccess && (getQuestionnaireStatusData(record, userDetails.data.regionCode) === “PENDING” || getQuestionnaireStatusData(record, userDetails.data.regionCode) === “INTERPOLATED”) ? true : false, }, { key: ‘4’, label: ‘View Branch approved’, }, { key: ‘2’, label: ‘Interpolate’, // disabled: isUserDetailsSuccess && (getQuestionnaireStatusData(record, userDetails.data.regionCode) === “CLEANED” || getQuestionnaireStatusData(record, userDetails.data.regionCode) === “INTERPOLATED” || getQuestionnaireStatusData(record, userDetails.data.regionCode) === “COMPUTED”) ? true : false, disabled: isUserDetailsSuccess && getQuestionnaireStatusData(record, userDetails.data.regionCode) !== ‘PENDING’ ? true : false, }, { key: ‘3’, label: ‘Create clean copy’, disabled: isUserDetailsSuccess && (getQuestionnaireStatusData(record, userDetails.data.regionCode) !== “INTERPOLATED”) ? true : false, } ] }
- Assistant
To accommodate for both situations, you can add a condition to check if the user is a director or a statistician. If the user is a director, the render function will display the status for all regions except for the user's own region. If the user is a statistician, the render function will only display the status for the user's own region. Here's the updated code:
render: (_, data) => { if (isUserDetailsSuccess) { const isDirector = userDetails.data.regionCode === undefined; const userRegionCode = userDetails.data.regionCode; let status = ''; if (data.questionnaireRegionStatus.length !== 0) { if (isDirector) { const qRegStatus = data.questionnaireRegionStatus.find(qRegStatus => qRegStatus?.regionCode !== userRegionCode); if (qRegStatus !== undefined) { status = qRegStatus.status; } } else { const qRegStatus = data.questionnaireRegionStatus.find(qRegStatus => qRegStatus?.regionCode === userRegionCode); if (qRegStatus !== undefined) { status = qRegStatus.status; } } } return renderQuestionnaireStatus(status); } else { return renderQuestionnaireStatus('-'); } }In this updated code, we first check if the user is a director by checking if their region code is undefined. If they are a director, we use
find()to search for the questionnaireRegionStatus object that has a regionCode that is not the user's region code. If they are a statistician, we usefind()to search for the questionnaireRegionStatus object that has a regionCode that matches the user's region code.If we find the appropriate questionnaireRegionStatus object, we set the
statusvariable to thestatusproperty of that object. We then pass thisstatusvariable torenderQuestionnaireStatus()to display the appropriate status. If we don't find the appropriate questionnaireRegionStatus object, we display a dash (-) as the status.
Other models, same or similar prompt
Responses were produced in different, uncontrolled contexts (system prompts, settings, prior turns). This is not a benchmark.