Actions
Bug #11374
closedIf Doc number field is set as Auto-Increment from Folder Management then for the new document, increment number is getting added with the last document number
Start date:
03/11/2019
Due date:
% Done:
0%
Estimated time:
Steps To Reproduce:
1.Go to Doc pro module
2.Click on folder management
3.Select any level
4.Select auto increment option for Document number
5.Click on New document request tab
6.Select the level
7.Observe result
MODULES:
DOCPRO
Build Cycle:
Cycle 4
Customer:
Issue Dependency:
Dev Commitment to Resolve in::
Description
Document number is not getting auto-populated,if Doc number field is set as Auto-Increment from Folder Management
Occurring in both website and Cascade DB
Files
Updated by Jacqueline Antonette about 6 years ago
- Status changed from Open to Resolved
Updated by Anonymous about 6 years ago
- Status changed from Resolved to Fixed with Hotfix
Updated by User Admin about 6 years ago
- Status changed from Fixed with Hotfix to Resolved
Updated by Anonymous about 6 years ago
- File Screenshot 001.png Screenshot 001.png added
- Subject changed from Document number is not getting auto-populated,if Doc number field is set as Auto-Increment from Folder Management to If Doc number field is set as Auto-Increment from Folder Management then for the new document, increment number is getting added with the last document number
Refer screenshot
Updated by Anonymous about 6 years ago
- Status changed from Resolved to Not Resolved
Updated by Jacqueline Antonette about 6 years ago
- Status changed from Not Resolved to Resolved
Not an issue
Updated by Anonymous about 6 years ago
- Status changed from Resolved to Fixed with Hotfix
Updated by Anonymous about 6 years ago
- Status changed from Fixed with Hotfix to Resolved
Updated by Anonymous about 6 years ago
- File 2019-04-02-DocIncrement.png 2019-04-02-DocIncrement.png added
- Status changed from Resolved to Not Resolved
Updated by Anonymous about 6 years ago
refer this 2019-04-02-DocIncrement.png Screenshot
Updated by Anonymous about 6 years ago
- Status changed from Not Resolved to Closed
As discussed with sabu,Its a valid issue, if we fix this it will create a impact. so closing this issue as of now and will add in future.
Actions