-
callbackregistration alert for reminding developer which flow is not running
Suggested by Klara LI – New – 0 Comments
Hi, it will be great that add a callbackregistration alert to help Pod developer find a Off flow or not actually running flow that don't include in the change solution. this will help a lot on developer manual efforts and reduce the production issues. thanks.
-
Allow deletion of WBS tasks when no actuals referencing them in the current legal entity
Suggested by Odile Hautenauve – New – 0 Comments
When we try to delete a task from a published wbs and try to publish the wbs again . we are getting an error message which says :
'You have deleted tasks from the WBS that have actuals reported against them. Publishing has failed and the WBS is still in draft and view differences has been enabled.'
This is on a wbs for a completely new project where we haven't done anything yet.
Actually it occurs not because a transaction has been posted against this task in the current legal entity but because there are several project actuals referencing this task in other legal entities.
-
Number sequence issue while transferring the Project Quotation to Project.
Suggested by Monika Upadhyay – New – 0 Comments
While transferring the Project Quotation to Project, it's observed the number sequence is not cleared from status list. This allows the system to pick up the already used number sequence for new projects and causing the issues.
Project Management and Accounting is core of customer's business and it’s a blocker for the business since the same number sequence is repeated and blocking the further projects creation with the error Project Id already used.
Below mentioned 2 workarounds were suggested but both are not feasible for following reasons:
- Turn Off the "continuous" number sequence: This is not feasible for the customer as it will cause the audit trial and compliance issue due to slippages of number (Project Id) in between. Also, It does cause revenue loss if the project is not timely created.
- Clear the status List: This is also not feasible as every user is not having access to this form and clear the list to proceed further.
Hence, we request you to take this as priority to fix the issue.
-
Make it possible to add a quarterly invoice frequency
Suggested by Marco de Vries – New – 0 Comments
It is not possible to create a quarterly invoice frequency so e.g. Advances invoices can't be generated automatically every quarter.
The options for the invoice frequency are Weekly, Monthly and Biweekly and it would nice to extend this with a Quarterly option.
-
Allow receipts to be uploaded at any time during new expense input
Suggested by Damon Greenshields – New – 0 Comments
Currently, when trying to input a new expense for an expense report, you are not able to upload receipts until you've input all the information boxes, and THEN hit the save button, at which point the program will flag you and tell you that receipts must be uploaded. Up until that point the upload buttons are greyed out. Needing to save the workbook in order to upload documents seems like a glitchy work around to a problem that shouldn't even be there. Why not just allow the receipts to be allowed at any point?
-
Add general budget reservation and add control budget
Suggested by Thierry Antorino – New – 0 Comments
In the expense management module, it should be possible to attach a general budget reservation to expense
In order to use this exepense management module for the public sector:
1) it would be necessary to provide for the possibility of attaching a budgetary reservation.
2) Establish budgetary control over expenses.
Because today this module expense management is unusable for the public sector.
-
Increase limitation on number of links within a project
Suggested by Supriya Anand – New – 0 Comments
Currently the limitation for links (dependencies) between tasks is set to 600 per project. Can this be extended to accommodate more links as we are currently always up against the limitation and having to split the products across different projects which isn't ideal.
-
Billing rule id to populate on associated transactions correctly
Suggested by Rekha Thattil – New – 0 Comments
When setup with a progress type billing rule, we noticed that when the invoice proposal is created it correctly assigns the billing rule.
But if you create a fee journal manually using the same category and bringing it in, billing rule is not associated correctly. Same happens if you try to use the 'Create Fees' on a current open invoice proposal.
Billing rules populating correctly on these transactions is essential because the Progress billing contract is tracking the contract & invoiced values against billing rule ids'. So if there is a data mismatch, the expected fee in the next round of billing is incorrectly calculated.
-
Sales Tax column at Line level displays zero amount
Suggested by Anukriti Anukriti – New – 0 Comments
When we create an invoice proposal, the sales tax amount is showing as zero in the line level of the invoice proposal transactions. We can see sales tax in the temporary sales tax table before posting but its not visible if we add the sales tax column in the transactions.
-
Project Budget Revision difference between Front end View vs. Detailed view - table rec ID overlap issue
Suggested by Mohammed Rizwan Azam – New – 0 Comments
Microsoft reference FinOps - 875531
we have worked on the table records and noted below bug in the code, could you please help us to fix this bug.
Generally the RecId and RevisionIds follow an incremental pattern which the query below (even you mentioned in repro doc) also assumes.
As validated from the customer data this assumption in below query is incorrect. The same we can reproduce by altering the RecIds in standard env.
while select RecId from budgetRevision
join RecId from projBudget order by budgetRevision.RevisionId
where projBudget.RecId == budgetRevision.ProjBudget
&& projBudget.RootProjId == projId
&&
budgetRevision.RecId <= this.RecId
Now as of this incident, we can mitigate it by correcting the RecIds of Revisions to follow same order as RevisionIds and all other tables where it is referenced.
However as we have the correct data in Details View (by clicking on Edit for each revision), I think it's better to fix this query itself.