Asta Powerproject version 16.0.01 release notes
This topic lists the new features that have been introduced, and the issues that have been addressed, in the Asta Powerproject version 16.0.01 release.
Issue | N/A | ||||
Category | Spreadsheet | ||||
Summary | Text formatting retained when copying and pasting spreadsheet data to and from other applications. | ||||
Description |
Using Asta Powerproject, you can apply formatting to individual spreadsheet cells, columns and rows, in the same way as you can using Microsoft Project and Microsoft Excel. Before this release, if you copied data from Microsoft Project or Microsoft Excel and pasted it into the Asta Powerproject spreadsheet - or if you copied data from the Asta Powerproject spreadsheet and pasted it into Microsoft Project or Microsoft Excel - any formatting that had been applied to the cells was lost.
Now, when you copy and paste data into or from the Asta Powerproject spreadsheet, any formatting that has been applied to the cells is retained. For example, if the text in a particular column has been coloured red, the text in a particular row has been formatted in bold italics and the text in a particular cell has been formatted with a particular font, this formatting information is retained when the data is copied and pasted.
You can specify the way in which cell formatting is pasted into Asta Powerproject, using the Pasting from other programs field that has been added to the Spreadsheet tab of the Options dialog. |
Issue | N/A | ||||
Category | Spreadsheet/Annotations | ||||
Summary | Apply strikethrough formatting to text. | ||||
Description |
You can now apply strikethrough formatting to text in the spreadsheet and to text in text annotations, using a new control that has been added to the Home tab of the Ribbon.
When you apply strikethrough formatting to text in the spreadsheet, it is applied to all of the text in the selected cell or cells. When you apply strikethrough formatting to text in a text annotation, you can apply it to the entire annotation, or to selected text within the annotation.
You can also apply strikethrough formatting to text in the spreadsheet using the Strike through check box that has been added to the Font tab of the Format Cells dialog; a corresponding check box has also been added to the Format Font dialog that you can use to configure the font of text annotations. |
Issue | N/A | ||||
Category | General | ||||
Summary | New dialog to help you deal with projects that fail to open. | ||||
Description | If you attempt to open a project and for some reason it fails to open, a new File Open Error dialog appears. This dialog gives the reason for the project's failure to open and gives you access to any backups of the project that you can open instead. |
Issue | N/A | ||||
Category | Backups | ||||
Summary | Specify the location in which backup files are stored. | ||||
Description |
|
Issue | N/A | ||||
Category | General | ||||
Summary | Better handling of projects that are located on a network drive. | ||||
Description |
Before this release, if you opened a project or baseline that was located on a network drive, Asta Powerproject opened the file directly. This could lead to problems if your network connection failed when the project was open.
Now, when you work with a project or baseline that is located on a network drive, Asta Powerproject does not open the project or baseline directly; it takes a copy of the project or baseline file, copies this to the temporary folder on your local computer, and opens this file. This improves performance when working with projects and baselines that are located on a network drives and reduces the possibility of file errors caused by network problems.
Each time you save, the original file on the network is synchronised with the local copy, in such a way to minimise the possibility of network errors causing problems during the save operation - the file being saved is saved under a new file name on the network, then this file is given the same name as the original file. For large files, a progress indicator appears each time this happens, indicating the progress of the save operation.
If a save operation to a network location fails, you are given the option to save the file to a different location.
While you work on a project or baseline that is located on a network drive, even though you are actually working on a local copy of the file, the project or baseline on the network drive is locked to prevent other users from accessing it. |
Issue | 22755 | ||||
Category | Printing/Date zone | ||||
Summary | Display shading between a range of dates in the date zone only when printing. | ||||
Description | A customer requested the ability to display shading between a range of dates in the date zone, rather than in the bar chart, in their printouts, to save ink. | ||||
Resolution | A Display date shading check box has been added to the General tab of the Date Zone Properties dialog. If you select this check box, date range shading is displayed in the date zone as well as in the bar chart. When printing, you can choose to display date range shading in the date zone only by clearing the Show date shading check box, in the 'Bar chart' section of the Appearance tab of the Print dialog. |
Issue | 26258 | ||||
Category | Bar chart | ||||
Summary | Remove individual shading selections from the bar chart temporarily. | ||||
Description | Before this release, if you had shaded the bar chart between two dates, it was not possible to remove individual shading selections from the bar chart temporarily; you had to either use a display switch to turn off all shading selections, or remove the shading selection permanently. A customer requested the ability to remove shading selections from the bar chart temporarily. | ||||
Resolution | You can now remove individual shading selections from the bar chart temporarily, using the Enabled check box that has been added to the Shading tab of the Date Zone Properties dialog. Select this check box to display a shading selection in the bar chart, or clear it to omit the shading section from the bar chart. |
Issue | 26305 | ||||
Category | Project view | ||||
Summary | Improve dragging and dropping of multiple objects from the project view. | ||||
Description | Before this release, if you wanted to assign multiple library objects from the project view to a task in the bar chart using drag and drop, you had to SHIFT or CTRL-click the objects in the project view, release SHIFT or CTRL, then SHIFT-click and drag the selected objects onto the task. This is not standard Windows behaviour. | ||||
Resolution | Now, you can assign multiple library objects from the project view to a task by simply SHIFT or CTRL-clicking the objects in the project view, keeping SHIFT or CTRL held down, and clicking and dragging the selected objects onto the task. This is standard Windows behaviour. |
Issue | 29255 | ||||
Category | Asta Site Progress | ||||
Summary | Accept or reject all items of progress at once. | ||||
Description | Before this release, when you used the Site Progress Mobile Approve Progress dialog to approve or reject progress that had been recorded remotely, you had to select the Accepted or Rejected check box for each item of progress individually. If the dialog displayed a large number of progress items, this could take some time. A customer requested the ability to accept or reject all items of progress at once. | ||||
Resolution | Accept All, Reject All and Clear All buttons have now been added to the bottom of the Site Progress Mobile Approve Progress dialog. You can use these buttons to accept or reject all items of progress at once. |
Issue | 30604 | ||||
Category | Bar chart | ||||
Summary | Give bar chart shading selections a more sensible default start date. | ||||
Description | Before this release, the start date of bar chart shading selections - on the Shading tab of the Date Zone Properties dialog - always defaulted to today's date, which made setting up shading selections less easy than it could have been. | ||||
Resolution |
Now, the start date of each new bar chart shading selection defaults to the day after the end of the latest shading selection in the grid. For example, if the latest shading selection in the grid had a finish date of 09/11/2021, the start date of the next shading selection you created would default to 10/11/2021.
There are two exceptions to this new behaviour:
|
Issue | 30657 | ||||
Category | Bar chart | ||||
Summary | Display code short names when displaying bar and task information in the bar chart. | ||||
Description | For each code library entry, you can specify a 'name' and a 'short name'. When you display the codes from a specific code library in the spreadsheet, you have always been able to specify whether to display each code's name or short name, but when displaying code names in the bar chart, you have only ever been able to display each code's name. A customer requested the ability to display the short name of each code in the bar chart. | ||||
Resolution | Now, when you display the names of codes from a specific code library in the bar chart, you can specify whether to display each code's name or short name, using the Use short name check box that has been added to the Attributes dialog. Select this check box to display the short name of each code in the bar chart, or clear the check box to display the name of each code. |
Issue | 30994 | ||||
Category | Access rights | ||||
Summary | Copy user options, as well as access rights, to subordinate users. | ||||
Description | Before this release, you could copy a user's access rights to one or more of their subordinate users, by right-clicking the user and selecting Clone Rights to Sub-Entries. This would display the Clone Rights dialog, which you could use to assign one or more subordinate users to the same security group as the selected user. However, this did not copy the selected user's options to the subordinate users - ie the fields that can be viewed as columns in the Library Explorer list view when viewing the Users library, by right-clicking a blank part of the list view and selecting Show All Fields. A customer requested the ability to copy these user options to subordinate users. | ||||
Resolution | Now, when you copy a user's access rights to one or more subordinate users, the selected user's options are copied to the subordinate users as well. The Clone Rights to Sub-Entries menu command has been renamed Clone Rights and Options to Sub-Entries, and the Clone Rights dialog has been renamed Clone Rights and Options. |
Issue | 31233 | ||||
Category | Formulae/Bar chart | ||||
Summary | Specify a progress period as a parameter for many fields in formulae and when displaying task data in the bar chart. | ||||
Description | Before this release, you could not specify a progress period as a parameter for fields in formulae or when displaying task data in the bar chart. This could lead to discrepancies between what was displayed in a field in the spreadsheet, and what was displayed in the same field in a formula or in the bar chart. For example, although you could configure a spreadsheet column to display the actual cost of tasks within a specific progress period, you could only display the actual cost of tasks in a formula or in the bar chart for all progress periods. | ||||
Resolution | Now, you can specify a progress period as a parameter for many fields in formulae and when displaying task data in the bar chart, using the Progress period field that has been added to the Select Object and Attributes dialogs. |
Issue | 31299 | ||||
Category | Asta Site Progress | ||||
Summary | Display live data rather than baseline data for in Asta Site Progress if there is a current baseline. | ||||
Description | Before this release, if a project had a current baseline, Asta Site Progress always displayed planned start and finish dates from the baseline rather than from the live project. A customer requested the ability to display planned start and finish dates from the live project rather than from the baseline. | ||||
Resolution |
You can now configure Asta Site Progress to display live data rather than baseline data, using the Use live project for planned dates/progress check box that has been added to the Export tab of the Site Progress Settings dialog. If you select this check box, the following fields display live data in Asta Site Progress:
If you clear the check box, the above fields display information taken from the current baseline, if a baseline is available. |
Issue | 31606 | ||||
Category | Access rights | ||||
Summary | Prevent users from editing project-wide dates. | ||||
Description | A customer requested the ability to prevent users from editing project-wide dates - the fields in the 'Dates' section of the Properties tab of the Backstage view. | ||||
Resolution |
You can now prevent users from editing project-wide dates, using the Edit project date controls check box that has been added to the General tab of the Security Group Properties dialog. If you clear this check box, members of the security group are prevented from editing the fields in the 'Dates' section of the Properties tab of the Backstage view, the corresponding fields on the Properties tab of the Properties dialog and - when viewing the properties of the programme chart - the date-related fields on the Project tab of the Chart/Project Properties dialog.
This field is selected by default in new projects and in projects that have been converted from an earlier version of Asta Powerproject. |
Issue | 31657 | ||||
Category | Calendar views | ||||
Summary | Calendar views display no tasks when Show multiple chart headers is selected. | ||||
Description | Before this release, if the Show multiple chart headers check box, on the View tab of the Options dialog, was selected, no tasks were displayed in calendar views when multiple charts or summary tasks were selected in the project view. | ||||
Resolution | Calendar views now display the contents of the charts or summary tasks that are selected in the project view when the Show multiple chart headers check box is selected. |
Issue | 31732 | ||||
Category | Progress | ||||
Summary | Configure the Planned percent complete (PPC) field to display a distributed average for parent tasks. | ||||
Description | A customer requested the ability to configure the Planned percent complete (PPC) field to display a distributed average for parent tasks. | ||||
Resolution |
You can now configure the Planned percent complete (PPC) field to display a distributed average for parent tasks, using the Show distributed average for charts/summaries check box, on the Table Definition Properties dialog.
If you select this check box, Asta Powerproject displays a progress value for expanded and summary tasks that takes into account how the progress is distributed within the subchart or summary group (a distributed average figure, which matches precisely the shading on expanded and summary tasks). If you clear this check box, a simpler value, which indicates the percentage of progress that has been completed without taking into account how the progress is distributed throughout the subchart or summary group, is displayed. |
Issue | 31803 | ||||
Category | Risk Analysis | ||||
Summary | Include partially-completed tasks in Risk Analysis calculations. | ||||
Description | Before this release, if you carried out risk analysis on a project in which progress had been recorded on one or more tasks, the progressed tasks would be excluded from the risk analysis. A customer requested that partially-completed tasks be included in Risk Analysis's calculations. | ||||
Resolution |
Although 100% complete tasks are still excluded from risk analysis, partially-completed tasks are now included: Risk Analysis generates new durations for the uncompleted sections of part-completed tasks in the same way as it does for tasks with no progress.
If the minimum value that you specify would result in a task being given a duration that is less than the duration of its completed section during an iteration, Risk Analysis does not reduce the duration of the task to make it 100% complete. If the maximum value that you specify is less than the duration of the completed section of a task, Risk Analysis excludes the task from the process and warns you. |
Issue | 31959 | ||||
Category | Sorting/Import and export | ||||
Summary | Use more appropriate calendars to calculate the duration of sort/group subheadings; apply more appropriate calendars to summary tasks when importing projects from Primavera software. | ||||
Description |
|
||||
Resolution |
|
Issue | 31964 | ||||
Category | Import and export | ||||
Summary | Match and update existing code libraries when importing projects from Primavera software. | ||||
Description | Before this release, if you applied a template when importing a project from Primavera software, and the template contained one or more code libraries with the same name as code libraries in the project you were importing, Asta Powerproject would create two code libraries with the same name in the resulting project. For example, if both the template and the project contained a code library called 'Location', the import would result in a project containing two 'Location' code libraries - one containing the codes from the template and the other containing the codes from the project you were importing. This behaviour was not ideal; in most cases, you would want the resulting project to contain a single 'Location' code library, containing both the codes from the template and the codes from the project. | ||||
Resolution | A Match existing code libraries check box has been added to the Primavera XML & XER Import Options dialog. If you select this check box when importing a project and applying a template, any code libraries with the same name in the template and project are combined into a single code library in the resulting project. If you clear this check box, the code libraries are not combined during the import, and the resulting project will contain two code libraries with the same name. |
Issue | 32023 | ||||
Category | Bar chart | ||||
Summary | Copy and paste date shading selections between views and projects. | ||||
Description | A customer requested the ability to copy date shading selections from one view and paste them into other views. | ||||
Resolution | You can now copy date shading selections, by right-clicking a shading selection on the Shading tab of the Date Zone Properties dialog and selecting Copy shading to clipboard. Once you have copied a shading selection to the Clipboard, you can paste it into another view - in a different project, if required - by accessing the Shading tab of the Date Zone Properties dialog in that view, right-clicking the grid and selecting Paste shading from clipboard. You can copy more than one shading selection at the same time, by CTRL-selecting the selections, then right-clicking one of them and selecting Copy shading to clipboard. |
Issue | 32075 | ||||
Category | Annotations | ||||
Summary | Text annotations that refer to baselines other than the current baseline fail. | ||||
Description | Before this release, if you created a text annotation containing a field that referenced a baseline other than the current baseline, the annotation would fail, with Asta Powerproject reporting a 'Baseline object not found or of incorrect type' message. | ||||
Resolution | This error was caused by Asta Powerproject using incorrect code when referencing baselines in text annotations. The code relating to using fields in text annotations has been improved, which has resolved this error. |
Issue | 32076 | ||||
Category | Baselines | ||||
Summary | Baseline merge fails to update task progress correctly. | ||||
Description | Before this release, if you adjusted the progress of a task with one or more outgoing links to 0% then merged this change into a baseline, the merge would fail to update the progress on the task in the baseline correctly; the completed section of the task would remain in the baseline. | ||||
Resolution | The baseline merge code has been updated to resolve this problem. |
Issue | 32108 | ||||
Category | Bar chart | ||||
Summary | Critical path appearance on 'necked' summary and hammock tasks differs from the rest of the project. | ||||
Description | Before this release, the critical path appeared on 'necked' summary and hammock tasks using a line with a width of a single pixel, rather than using the specified line style. | ||||
Resolution | The critical path now appears on 'necked' summary and hammock tasks correctly. |
Issue | 32143 | ||||
Category | Asta Powerproject 4D | ||||
Summary | Unable to open an IFC file in Asta Powerproject 4D. | ||||
Description | A customer reported that when they tried to open a particular IFC file, Asta Powerproject 4D reported a 'Eleco.BIM.IFC2x3.IfcDerivedProfileDef doesn't define DefineCrossSection' error, then the IFC Model pane stopped responding. It was possible to open the IFC file in other applications. | ||||
Resolution | The IFC file in question used transformed profiles, which were not supported in Asta Powerproject 4D. Asta Powerproject 4D can now open such IFC files without any issues. |
Issue | 32166 | ||||
Category | Bar chart | ||||
Summary | Bar chart flickers then goes blank when coloured progress shading is displayed on baseline summary tasks. | ||||
Description | A customer reported that when they imported a Microsoft Project file as a baseline and applied a template to it, then displayed the baseline and progress shading in a view, the bar chart flickered then went blank. | ||||
Resolution | The view in question displayed coloured progress shading on baseline summary tasks. The baseline used a progress period that did not exist in the live data and Asta Powerproject was referring to the live data rather than the baseline to look up the progress period, which caused this problem. Asta Powerproject now refers to the baseline to look up progress periods when applying progress shading to baselines, which has resolved the problem. |
Issue | 32199 | ||||
Category | Asta Site Progress | ||||
Summary | Include the path to the task when copying Site approve progress data to the Clipboard. | ||||
Description | When you approve progress using the Site Progress Mobile Approve Progress dialog, the path of each task is displayed on the dialog. Before this release, this path information was not included if you clicked the Copy to Clipboard button to copy task data to the Clipboard. A customer requested that the path of each task be included in the copied data, to make it easier to identify the location of each task in the project. | ||||
Resolution | The path of each task is now included when you click Copy to Clipboard on the Site Progress Mobile Approve Progress dialog. Also, tasks are now grouped by parent chart in the copied data. This makes it easier to identify the location of each task in the project. |
Issue | 32217 | ||||
Category | Book in and out | ||||
Summary | Security problem when booking out a project from a master file. | ||||
Description | Before this release, if you booked out a section of a project and opened the booked-out file, the file displayed only the section of the project that had been booked out. However, if you saved the booked-out file with a different file name then closed and re-opened the new copy of the file, it displayed the entire project - not just the booked-out section. | ||||
Resolution | It is no longer possible to access an entire project by saving a booked-out section with a different file name. |
Issue | 32228 | ||||
Category | Resource usage view | ||||
Summary | Resource usage view toggle control on the status bar does not have an icon. | ||||
Description | Since the release of Asta Powerproject version 15, the icon for the resource usage view toggle on the status bar was missing. | ||||
Resolution | The icon for the resource usage view toggle on the status bar has been reinstated. |
Issue | 32229 | ||||
Category | Calendars | ||||
Summary | Missing icons in the Add Exception dialog. | ||||
Description | Since the release of Asta Powerproject version 15.0.02, the 'clock' icons that should appear to the left of each exception type in the Exception type field on the Add Exception dialog were missing. | ||||
Resolution | The 'clock' icons have been reinstated in the Exception type field on the Add Exception dialog. |
Issue | 32243 | ||||
Category | Unique task ID numbering | ||||
Summary | Unique task IDs are not assigned to summary or expanded tasks that are inserted via the project view. | ||||
Description | A customer reported that if they inserted summary or expanded tasks into a project via the project view, Asta Powerproject did not assign unique task IDs to them. Also, if the customer created a task on the bar immediately beneath the new summary or expanded task, Asta Powerproject would assign a unique task ID to it but it would not include the appropriate prefix. | ||||
Resolution | Asta Powerproject now assigns unique task IDs to summary and expanded tasks that are inserted via the project view; tasks that are created immediately beneath these new summary and expanded tasks are now assigned unique task IDs that include the appropriate prefix. |
Issue | 32253 | ||||
Category | Costs | ||||
Summary | When allocating costs via the spreadsheet, default assignment properties of the cost centre are not applied to the allocation. | ||||
Description | Before this release, if you allocated a cost to a task via the spreadsheet - by entering a value into a cost column that was configured to point to a particular cost centre - the cost centre's default assignment properties would not be applied to the resulting cost allocation. For example, if the cost centre was configured to have 'point spend' allocations by default, this would be ignored when allocating costs via the spreadsheet. | ||||
Resolution | Asta Powerproject now respects the default assignment properties of cost centres when you allocate costs to tasks via the spreadsheet. |
Issue | 32258 | ||||
Category | Import and export | ||||
Summary | Unknown exception when exporting a project to Primavera software in XER or XML format. | ||||
Description | A customer reported that when they attempted to export a project to Primavera software in XER or XML format, an 'Unknown exception occurred (bad optional access)' error occurred. | ||||
Resolution | The project in question contained a number of permanent resources to which no calendar had been assigned, which caused this problem. During the export process, Asta Powerproject now assigns the default calendar to any permanent resources to which no calendar has been assigned, which resolves this issue. |
Issue | 32299 | ||||
Category | Block-linking | ||||
Summary | Missing icons in the Block Link Method dialog. | ||||
Description | Since the release of Asta Powerproject version 15.0.02, the icons that should appear in the Block Link Method dialog were missing. | ||||
Resolution | The icons have been reinstated in the Block Link Method dialog. |
Issue | 32302 | ||||
Category | Asta Powerproject 4D | ||||
Summary | Some objects in an IFC model are shown to have a negative volume. | ||||
Description | A customer reported that some objects in an IFC model were shown to have a negative volume. Some of the floors in the IFC model had inconsistently facing faces (parts of the perimeter facing inwards) and physically-impossible surfaces that branched. These problems meant that Asta Powerproject 4D could not calculate the volumes correctly. | ||||
Resolution | Asta Powerproject 4D is now able to correct errors involving inconsistently facing faces. However, errors involving physically-impossible surfaces require manual intervention to fix, by editing the IFC file. As incorrect values can be misleading, Asta Powerproject 4D no longer attempts to calculate volumes for objects with physically-impossible surfaces. |
Issue | 32324 | ||||
Category | Asta Powerproject 4D | ||||
Summary | IFC colours do not show up in Asta Powerproject 4D. | ||||
Description | A customer reported that when they opened an IFC file in Asta Powerproject 4D, the model's colours were not displayed; everything appeared in a grey colour. | ||||
Resolution | The error that caused the IFC model's colours to be omitted from the display has been addressed. |
Issue | 32330 | ||||
Category | Reschedule | ||||
Summary | ALAP tasks with negative float are positioned incorrectly after a reschedule. | ||||
Description | A customer reported that when the Negative float applies to chain reschedule option was selected, ALAP tasks were given negative float and were positioned incorrectly after a reschedule. | ||||
Resolution | Before this release, late start and late finish dates were used to position ALAP tasks in this situation; now, free start and free finish dates are used. This means that when the Negative float applies to chain reschedule option is selected, ALAP tasks are now positioned correctly after a reschedule. |
Issue | 32344 | ||||
Category | Dialogs | ||||
Summary | Cost and Income fields display the wrong information in the Project Properties dialog. | ||||
Description | Before this release, the Cost field, on the Project tab of the Project Properties dialog, displayed a project's income, and the Income field displayed a project's cost. | ||||
Resolution | The Cost and Income fields on the Project tab of the Project Properties dialog now display the correct information. |
Issue | 32350 | ||||
Category | User-defined fields/Import and export | ||||
Summary | Create user-defined fields with names that include space characters. | ||||
Description | Primavera software enables you to create user-defined fields with names that include space characters - for example, 'Field 1'. Before this release, Asta Powerproject did not allow user-defined field names to include space characters, and Asta Powerproject converted any space characters in user-defined field names to underscores when you imported a project from Primavera software. For example, a Primavera user-defined field called 'Field 1' would be converted into an Asta Powerproject user-defined field called 'Field_1'. This resulted in duplicate user-defined fields in projects that were transferred backwards and forwards between Primavera software and Asta Powerproject. | ||||
Resolution | You can now include space characters in the names of user-defined fields in Asta Powerproject. This enables you to transfer projects backwards and forwards between Primavera software and Asta Powerproject without any changes being made to the names of user-defined fields. |
Issue | 32353 | ||||
Category | General | ||||
Summary | Improvements to the dialogs used to open and save projects. | ||||
Description | A request was made for the dialogs you access by clicking Browse to open and save projects to be updated. | ||||
Resolution | The dialogs that you use to open and save projects have been updated to improve their look and feel. In addition, you now use separate dialogs to open and save Asta Powerproject Enterprise projects. When using Asta Powerproject Enterprise, drop-down arrows appear to the right of a number of buttons throughout the user interface, enabling you to specify whether you are working with a local project or an Asta Enterprise project. |
Issue | 32365 | ||||
Category | Dialogs | ||||
Summary | Accessing the New Link dialog causes Powerproject to close. | ||||
Description | A customer reported that when they clicked Add Link on the Links tab of the Bar and Task Properties dialog, Asta Powerproject would close; sometimes the New Link dialog would appear, but Asta Powerproject would close if they clicked More on this dialog. | ||||
Resolution | The error that caused Asta Powerproject to close in this situation has been resolved. |
Issue | 32451 | ||||
Category | Licensing | ||||
Summary | Inform users if it is not possible to connect to the Sentinel Cloud when attempting to activate a Sentinel licence. | ||||
Description | Before this release, if Asta Powerproject was unable to connect to the Sentinel Cloud when attempting to activate a Sentinel licence, it presented you with a red cross on the activation dialog, with no further information. | ||||
Resolution | Now, if Asta Powerproject is unable to connect to the Sentinel Cloud when attempting to active a Sentinel licence, the activation dialog presents you with an error and a Retry button, which enables you to attempt the activation again after any Internet connection issues have been resolved, without having to exit the activation routine and start again from scratch. |
Issue | 32453 | ||||
Category | Asta Vision/Asta Enterprise | ||||
Summary | If a check out is cancelled, the checked-out programme remains on the Asta Enterprise server. | ||||
Description | Before this release, if you checked out a programme from Asta Vision to an Asta Enterprise server, then cancelled the check out, the programme remained on the Enterprise server, which prevented the programme from being checked out again. | ||||
Resolution | Now, if you check out a programme from Asta Vision to an Asta Enterprise server, then cancel the check out, the programme is moved from the Enterprise server into your 'Backup Files' folder, as specified on the File Locations tab of the Options dialog. This means that you can check the programme out subsequently. |
Issue | 32556 | ||||
Category | Asta Enterprise | ||||
Summary | Remove the Microsoft SQL Server user name and password from the Windows application log. | ||||
Description | A customer reported that if Asta Enterprise fails to connect to the Microsoft SQL Server database, the failure that is reported in the Windows application log includes the SQL Server user name and password. The customer requested that this information be removed from the log, as the information could be seen by people who do not usually have access to it. | ||||
Resolution | The Microsoft SQL Server user name and password have been removed from the Windows application log. |
Issue | 32566 | ||||
Category | Code libraries | ||||
Summary | Unable to remove codes from 100% complete milestones, summary tasks and expanded tasks. | ||||
Description | Since the release of Asta Powerproject version 15.0.01, if you tried to remove a code from a 100% complete milestone, an error would result; if you tried to remove a code from a 100% complete summary task or expanded task, Asta Powerproject would crash. | ||||
Resolution | The error has caused this to happen has been resolved. |
Issue | 32680 | ||||
Category | Licensing | ||||
Summary | Inform the user if they attempt to use a product key that has been activated on another computer. | ||||
Description | Before this release, if a customer attempted to use a product key that had already been activated (and not deactivated) on another computer when activating Asta Powerproject, the customer was not informed of this; Asta Powerproject appeared to be activated, but remained in 'Trial' mode. | ||||
Resolution | If a customer now attempts to use a product key that has already been activated on another computer, Asta Powerproject now warns 'Failed to acquire licence. Maximum station count limit reached'. If this error appears, the product key needs to be deactivated on another computer before it can be used on the new computer. |