Package Description
$ dotnet add package Indice.Features.Cases.UIAll notable changes to this project will be documented in this file.
The format is based on Keep a Changelog, and this project adheres to Semantic Versioning.
UnauthorizedComponent from Indice.Angular library to handle Forbidden requests.GridColumnConfig property to CaseType, you can change your lib-list-view to display custom columns.IsMenuItem property to CaseType, you can now have all your cases displayed in a separate category as a menu item based on their case typeGridFilterConfig property to CaseType, you can add a case type specific filter to your searchOptions dropdown.For example, you can edit a case type from the UI and put a
SearchOptionjson formatted string like so:
[
{
"field": "RequestId",
"name": "REQUEST ID",
"dataType": "string"
}
]
Αίτηση -> Υπόθεσηlabel-only widget component has been extended to handle href elements.label-only widget component has been extended to handle elements that need data-binding from other form data, eg. extraType = "data-bind".label-only widget component are now displayed correctly.label-only widget component to handle form input data as a simple label in cases BackOffice. Supports enum, currency & bool type conversions.href widget component to handle links in cases backoffice.cases.referenceNumber & caseDetails.referenceNumberExample to override the visible filters & columns
app.UseCasesUI(options => {
// Filter using only: ReferenceNumber, CustomerId, CustomerName,
// TaxId, CaseTypeCode
options.CaseListFilters = new HashSet<CaseListFilter>() {
CaseListFilter.ReferenceNumber,
CaseListFilter.CustomerId,
CaseListFilter.CustomerName,
CaseListFilter.TaxId,
CaseListFilter.CaseTypeCodes,
};
// Display only the columns: ReferenceNumber, CustomerId,
// CustomerName, TaxId, CaseType, AssignedTo. SubmitDate
options.CaseListColumns = new HashSet<CaseListColumn>() {
CaseListColumn.ReferenceNumber,
CaseListColumn.CustomerId,
CaseListColumn.CustomerName,
CaseListColumn.TaxId,
CaseListColumn.CaseType,
CaseListColumn.AssignedTo,
CaseListColumn.SubmitDate
};
});
checkpointType.status.ng-indice classes were overriding back-office action buttons, making them transparent.dashboard, cases, case-details pages using @ngx-translate.Example to override default el.json file
app.UseCasesUI(options => {
// This is the absolute path to the folder that contains the el.json
options.I18nAssets = "/assets/cases/i18n";
});
Example enabling only two canvases
app.UseCasesUI(options => {
options.DashboardTags = new List<string>() {
"GroupedByCasetype",
"GroupedByStatus"
};
CheckpointType Translations to cases list, checkpointtype filter, case details and timeline.checkpointsThatAllowDownload as a case type Config optioncase-channel that indicates whether the field is visible based on case's channel.ngx-quillcurrency-widgetLang at CasesUIOptions for handling the attribute <html lang='XXX'> from the options.This change will require from the consumer api to handle the language. Eg:
app.UseCasesUI(options => {
// ...
options.Lang = "el";
});
case.metadata propertyexample layout that sets the data.isLegal property
{
"backoffice": [
{
// mv: modelValue, f: form (entity), md: case metadata
"onInit": "function(mv,f,md) {f = f || {}; if(md.LegalEntity === '1' || md.LegalEntity.toLowerCase() === 'true') {f.isLegal = true;} return f; }",
...
]
}
notifications route can only be seen & navigated by non-admin userslib-toggle-button component from @indice/ng-components npm package@indice/ng-components npm package latest versionJSON.stringify(data) is no longer needed to send json data to a case. Case data request is dynamic.JSON.parse(data) is no longer needed for parsing. Case data response is dynamic.date-widget through layout options