Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[TM-6077] Re-Integrate Publishable Positions Edit #1004

Merged
merged 10 commits into from
Jun 12, 2024

Conversation

jlam-mpc
Copy link
Collaborator

@jlam-mpc jlam-mpc commented May 31, 2024

Dual Merge:

TM-6077

@jlam-mpc jlam-mpc added WIP Work in progress and removed WIP Work in progress labels May 31, 2024
Comment on lines -165 to +174
'PV_API_VERSION_I': '',
'PV_AD_ID_I': '',
'I_POS_SEQ_NUM': request.get('posSeqNum') or '',
'I_PPOS_CAPSULE_DESCR_TXT': request.get('positionDetails') or '',
'I_PPOS_LAST_UPDT_USER_ID': request.get('lastUpdatedUserID') or '',
'I_PPOS_LAST_UPDT_TMSMP_DT': request.get('lastUpdated') or '',
'pposposseqnum': request.get('posSeqNum') or '',
'ppospubscd': request.get('psCD') or '',
'pposaptsequencenum': request.get('aptSeqNum') or '',
'pposcreatetmsmpdt': request.get('created') or '',
'pposcreateuserid': request.get('createdUserID') or '',
'pposcapsulemodifydt': request.get('positionDetailsLastUpdated') or '',
'pposauditexclusionind': request.get('posAuditExclusionInd') or '',
'pposcapsuledescrtxt': request.get('positionDetails') or '',
'pposlastupdttmsmpdt': request.get('lastUpdated') or '',
'pposlastupdtuserid': request.get('lastUpdatedUserID') or '',
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Keep in mind that the original edit was only for capsule descriptions.

The new edit will encapsulate everything, but also means we have to consider how we want to break up the functionality. Should the API allow for all editing by anyone? How do we break out AOs editing everything, but bureaus/post only editing capsule? On FE only, API route protections, role checks inside the edit to determine if the field should be modifiable etc.?

We want to make sure the underlying service for edit PPOS can be vetted through our API based on the correct roles

Copy link

@cagbakwu cagbakwu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Outside of Scotts comment, it looks good 🫡
Screenshot 2024-06-11 at 2 45 43 PM

@jlam-mpc jlam-mpc merged commit e0720b0 into dev Jun 12, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
5 participants