Automate

Hello,

we've some trouble with our dashboard because of the review date in the process history in documents.

When a user open the document first time a review date/time is set up automatically.

Sometimes happens that the document cannot be finished directly and user close the document and open it later again.

Unfortunately, the review date in the process history will not updated with the new date/time and this is causing problems in our dashboard calculation.

Usually we've a seperate timestamp inside the solutions, but these data are not transferred to the Archive base.

Is it possible to adjust the archive base to get single columns from solution or is there a possibility to change something in the App that review date will be updated according according to the last opening time?

Many thanks in advance.

Claudia

Hi Claudia

I believe the review date is as designed, i.e. the first review date.

You can do what we call "promote" a field to be included in the Evolve database.  Go to the field properties and give the field a name in the Promote to Solution Field

Once you deploy, any value in there will end up in a reporting view for that solution in the specific app. For example, I have a solution called BPRequestwithSalesforceandDISAPIs  in this app Sigrid, and it is an Evolve form solution  so the view is called: RPT_BPRequestwithSalesforceandDISAPIs_EVO_SIG_FOR

• RPT for reporting
• the solution name
• EVO is Evolve
• SIG for the first 3 letters of the app name
• FOR for a form solution.

You can join that with the standard reporting views on tasks to incorporate an updated review date.

Here's some output from that BP create solution

It's very specific to a solution and the promoted fields in that solution.  Note that if you add a solution field, all prior entries will have a blank field for the field.  All new workflow instances will populate that field.

I hope this gives you some ideas.

Best Regards,

Sigrid

Hello,

we've some trouble with our dashboard because of the review date in the process history in documents.

When a user open the document first time a review date/time is set up automatically.

Sometimes happens that the document cannot be finished directly and user close the document and open it later again.

Unfortunately, the review date in the process history will not updated with the new date/time and this is causing problems in our dashboard calculation.

Usually we've a seperate timestamp inside the solutions, but these data are not transferred to the Archive base.

Is it possible to adjust the archive base to get single columns from solution or is there a possibility to change something in the App that review date will be updated according according to the last opening time?

Many thanks in advance.

Claudia

I'm not sure if this will solve the problem.

In our dashboard the ArchiveBase on the SQL Server is connected, but it shows not the populated/promoted fields we need. 

I guess is also as designed.

We're not pulling data via report.

Any other suggestion? Or may I missunderstood your reply before?

Kind regards,

Claudia

Hi Claudia

I believe the review date is as designed, i.e. the first review date.

You can do what we call "promote" a field to be included in the Evolve database.  Go to the field properties and give the field a name in the Promote to Solution Field

Once you deploy, any value in there will end up in a reporting view for that solution in the specific app. For example, I have a solution called BPRequestwithSalesforceandDISAPIs  in this app Sigrid, and it is an Evolve form solution  so the view is called: RPT_BPRequestwithSalesforceandDISAPIs_EVO_SIG_FOR

• RPT for reporting
• the solution name
• EVO is Evolve
• SIG for the first 3 letters of the app name
• FOR for a form solution.

You can join that with the standard reporting views on tasks to incorporate an updated review date.

Here's some output from that BP create solution

It's very specific to a solution and the promoted fields in that solution.  Note that if you add a solution field, all prior entries will have a blank field for the field.  All new workflow instances will populate that field.

I hope this gives you some ideas.

Best Regards,

Sigrid

Hello,

we've some trouble with our dashboard because of the review date in the process history in documents.

When a user open the document first time a review date/time is set up automatically.

Sometimes happens that the document cannot be finished directly and user close the document and open it later again.

Unfortunately, the review date in the process history will not updated with the new date/time and this is causing problems in our dashboard calculation.

Usually we've a seperate timestamp inside the solutions, but these data are not transferred to the Archive base.

Is it possible to adjust the archive base to get single columns from solution or is there a possibility to change something in the App that review date will be updated according according to the last opening time?

Many thanks in advance.

Claudia

Hi Claudia

You would have to 

(1) promote the updated review data in the solution, if you haven't already

(2) The RPT.... view I described in my reply would have the field in it

(3) if you are including archived data, you would also need the RPT.....view that I described in my reply - whether in the archive or live db

(3) you would join the activity view table with the RPT.... view that goes along with your solution, and then you can calculate the updated review date calculation in your report - typically this is done by workflow instance name - here's an example I built in Evolve v20.x - swap in your solution view info, app name and dbname (instead of WSEvolveDBGA) See fields in green to swap out, and add your promoted review date from the solution fields, plus anything else you need in your report.  My example below is for a Business Partner create solution.

SELECT  

/* process view */ 

[ProcessName]       ,p.[SolutionName]       ,[AppName]           ,[LibraryName]       ,p.[Status]

,[CreationDate]       ,[CompletionDate]       ,[Originator]      

,[UserId]       ,[CreationDateDiff]      ,[DueDate]

,[IsCreatedToday]      ,[IsCompletedToday]      ,[IsPassedDueDate]    

,[IsRunning]      ,[IsCompleted], [Originator]

 /* solution view */

,[BPNumber]   ,[City]        ,[ckCanceled]     

,[Company_Code] , [Country_Key]       ,[Distribution_Channel]       ,[Division]   , [Purchasing_Org]   

,[flagCustomerOrSupplier]       

,[LogField_CustCompany]       ,[LogField_CustSales]       ,[LogField_General]      

,[Name_1_of_organization], [City]

,[Sales_Organization]       ,[SolutionFormName], [RegionState]

,[Title]      ,[CreatedByDisplayName] 

/* process status */ 

 ,ps.[Description] as StatusDescription

 FROM [WSEvolveDBGA].[dbo].[RPT_BusinessPartner-Create-S4Hana_EVO_SED_FOR] s,  [WSEvolveDBGA].[dbo].[RPT_ProcessReportingDetailsView] p,  [WSEvolveDBGA].[dbo].[WF_ProcessStatus] ps

WHERE s.[DataFileID]   = p.[DataFileID] and p.AppName='SEDemo' and p.SolutionName='BusinessPartner-Create-S4Hana'  and s.Status=ps.Code

Does that make sense?

Hope so!

Sigrid

I'm not sure if this will solve the problem.

In our dashboard the ArchiveBase on the SQL Server is connected, but it shows not the populated/promoted fields we need. 

I guess is also as designed.

We're not pulling data via report.

Any other suggestion? Or may I missunderstood your reply before?

Kind regards,

Claudia

Hi Claudia

I believe the review date is as designed, i.e. the first review date.

You can do what we call "promote" a field to be included in the Evolve database.  Go to the field properties and give the field a name in the Promote to Solution Field

Once you deploy, any value in there will end up in a reporting view for that solution in the specific app. For example, I have a solution called BPRequestwithSalesforceandDISAPIs  in this app Sigrid, and it is an Evolve form solution  so the view is called: RPT_BPRequestwithSalesforceandDISAPIs_EVO_SIG_FOR

• RPT for reporting
• the solution name
• EVO is Evolve
• SIG for the first 3 letters of the app name
• FOR for a form solution.

You can join that with the standard reporting views on tasks to incorporate an updated review date.

Here's some output from that BP create solution

It's very specific to a solution and the promoted fields in that solution.  Note that if you add a solution field, all prior entries will have a blank field for the field.  All new workflow instances will populate that field.

I hope this gives you some ideas.

Best Regards,

Sigrid

Hello,

we've some trouble with our dashboard because of the review date in the process history in documents.

When a user open the document first time a review date/time is set up automatically.

Sometimes happens that the document cannot be finished directly and user close the document and open it later again.

Unfortunately, the review date in the process history will not updated with the new date/time and this is causing problems in our dashboard calculation.

Usually we've a seperate timestamp inside the solutions, but these data are not transferred to the Archive base.

Is it possible to adjust the archive base to get single columns from solution or is there a possibility to change something in the App that review date will be updated according according to the last opening time?

Many thanks in advance.

Claudia