I added a new date field, cstReminderDateDA, to a custom business object. For existing records, there is a requirement that cstReminderDate be set to the value of an existing date field (cstDueDateDA) minus 30 days, i.e. cstReminderDateDA = (cstDueDateDA – 30). This would be pretty straightforward, except that both cstReminderDateDA and cstDueDateDA are stored as numeric fields in our Microsoft SQL Server database. How do I populate cstReminderDateDA?
IBM TRIRIGA stores the date as epoch time. See the following wiki link explaining this. If you do some searching, you will find some functions available for SQL Server for data calculations.
[Admin: To see other related posts, use the Epoch Time tag.]
What is the best way to handle calculated fields that need to reference the Current Date or System Date? For example, I have a number field in the Building BO called Building Age. To calculate the Building Age, I had to create another field called “cstCurrentDateDA” to store the current date the Building record was created.
From there, I take the Current Date minus the In Service Date of the building. However, let’s say I wanted the Building Age field to get updated daily. In my current design, I would have to probably create an asynchronous workflow to update the “cstCurrentDateDA” field and then trigger a Save action to get the extended formula against the Building Age field to fire.
Is there a better approach to dealing with field variables that rely on the Current Date or System Date? Instead of creating a custom field to store the Current Date to act as a constant factor?
[Admin: To see other related posts, use the Date tag.]
When the Operations team was changing a job plan, the wrong date was entered, and it created over 1,800 work tasks. They have since tried to retire them and they changed to Draft status. To get rid of these, can the job plan itself be retired?
[Admin: To see other related posts, use the Job Plan tag.]
Filtering on a word in a date or date-time column produces unexpected results.
The platform treated any invalid string as “Today’s Date”. Moving forward, for query reports that have filters enabled, a check was added whenever a user attempts to use an invalid filter in a date or date-time field. If a non-date or non-date-time string is used in this filter, then a “No data to display” message is shown to the user in the body of the query results table, and zero results are returned.
[Admin: To see other related posts, use the Date tag or Filter tag.]
We would like to upload a date in “dd.mm.yyyy” format. As long as TRIRIGA doesn’t support this format, what would be the best way to transform a string with “dd.mm.yyyy” to Epoch date, and then copy it to a Date field inside TRIRIGA? For example, advanced formula, custom task, etc.?
I think one of the possible ways is to leverage an ETL tool (e.g. Kettle Spoon) to transform data. See the Data Management (PDF) user guide.
[Admin: To see other related posts, use the ETL tag.]
Our workflow sends an outbound message by user action. For the Connector for Business Applications (CBA), the Connector user guide says:
For date values, the outbound query results include the raw values that are stored in the database and the formatted display values that are shown to the user. The displayValue node is added to the query results. The following example shows the default XML structure…
But for us, the outbound message has a different format… The <value> is presented in the same way as <displayValue> which is not acceptable because users may have a different date format. Is there a way to get the proper date value in <value> or use a single <displayValue> format for all users?
In TRIRIGA, why doesn’t my dependent task go any further than the planned end date, if I move the parent task beyond the planned end date?
The task that is being moved (along with its dependent task) eventually violates the planned end constraint. The task that is in violation of the constraint is in red, and the dependent task will not be moved past the planned end. If there is no planned end, then there is no constraint and you can freely move both tasks.
[Admin: To see other related posts, use the Gantt tag or Scheduling tag.]