New table structure for storing OTP/Tokens for application
Question:
Please find some new table structure for storing OTP/Tokens for application and changes for discretion:
Please find some new table structure for storing OTP/Tokens for application and changes for discretion:
| TabelName | ColumnName | Type | | Method | Parameter |
| B_ProposalUser_OTP | ID | INT | | Create() | PropsalID,MsgID |
| | ProposalID | INT | | Update() | PropsalID,MsgID |
| MsgID | INT | | GetDetailsById | PropsalID,MsgID,TokenType,PersonID,Satus | |
| PersonID | INT | | UpdateByTokenString() | PropsalID,MsgID,TokenString | |
| MobileNo | Varchar | | |||
| EmailID | Varchar | | |||
| TokenType | tynint | Developer | |||
| TokenString | Varchar | | |||
| FailedAttempts | INT | | |||
| Status | tynint | 0-Pending 1-Verified 2-Expired | |||
| GeneratedOn | DateTime | | |||
| ValidTill | DateTime | | |||
| | Create() | PUOID | |||
| B_ProposalUser_OTPAttempts | ID | INT | | Update() | PUOID |
| | PUOID | INT | | GetDetailsById | PUOID,ActionTaken |
| AttemptOn | DateTime | | |||
| AttemptStatus | tynint | Fail/Pass | |||
| ActionTaken | tynint | 0-NA 1-Accept 2-Reject | Need discussion for placing of these column | ||
| ActionDate | DateTime | | |||
| | |||||
| B_SanctionPlots | MsgID | INT | | ||
| | |||||
| BP_DiscretionGroup | MsgID | INT | | ||
| | PlanSubmissionNo | INT | | ||
| | |||||
| BPPMC_Discretion | MsgID | INT | | ||
| | PlanSubmissionNo | INT | | ||
| | No direct Link between above table | | | ||
| BP_Proposal_Status | IsVerifyByDeveloper | tynint | 0-NA 1-Accept 2-Reject |

Get help for this page
