Description

Add a layer on top of the import API to make import requests easier to use. At the moment, requests are defined as follows:

ImportRequest importRequest = new ImportRequest(
  "mboc_upsertCategory",
  new List<string> { "Name", "Color" }.ToArray(),
  new List<string> { "Category #1","#6e62b5" }.ToArray()
);

This is overly complex and unnecessary. Therefore, the following actions are recommended:

• Do not expose stored procedure names
• Dedicated parameters with appropriate types
• Add validation to the mix

Import endpoints

• mboc_addAppointmentResource
• mboc_clearResourceFilterValue
• mboc_clearTaskFilterValue
• mboc_deleteAppointment
• mboc_deleteAppointmentContainer
• mboc_deleteCategory
• mboc_deleteContainer
• mboc_deleteExchangeAppointment
• mboc_deleteFilterGroup
• mboc_deleteFilterValue
• mboc_deleteJob
• mboc_deleteNotification
• mboc_deletePin
• mboc_deleteResourceCalendar
• mboc_deleteResourceCertificate
• mboc_deleteResourceFilterValue
• mboc_deleteTask
• mboc_deleteTaskContainer
• mboc_deleteTaskFilterValue
• mboc_deleteTimeMarker
• mboc_updateAppointmentCategory
• mboc_updateAppointmentContent
• mboc_updateAppointmentImportance
• mboc_updateAppointmentLocked
• mboc_updateAppointmentPlanningQty
• mboc_updateAppointmentTimeMarker
• mboc_updateTaskLocked
• mboc_upsertActionUrl
• mboc_upsertAppointment
• mboc_upsertAppointmentContainer
• mboc_upsertAppointmentUrl
• mboc_upsertCaption
• mboc_upsertCategory
• mboc_upsertContainer
• mboc_upsertExchangeAppointment
• mboc_upsertFilterGroup
• mboc_upsertFilterValue
• mboc_upsertJob
• mboc_upsertNotification
• mboc_upsertPin
• mboc_upsertResource
• mboc_upsertResourceCalendar
• mboc_upsertResourceCapacity
• mboc_upsertResourceCertificate
• mboc_upsertResourceFilterValue
• mboc_upsertResourceGpsTracking
• mboc_upsertResourceUrl
• mboc_upsertTask
• mboc_upsertTaskContainer
• mboc_upsertTaskFilterValue
• mboc_upsertTaskUrl
• mboc_upsertTimeMarker

Remove duplicate parameters and reuse URI and authentication token in the authenticator and endpoint service.

string uri = "http://localhost:53006/";
DimeSchedulerClient client = new(uri);
await client.Authenticate("[email protected]", "Password123");

ImportRequest importRequest = new(
    "mboc_upsertExchangeAppointment",
    new List<string>{}.ToArray(),
    new List<string>{}.ToArray())
{
    Uri = uri, // Already available so should not declare twice
    AuthenticationToken = client.AuthenticationToken // Already available so should not declare twice
};

Furthermore, find a more elegant solution IRequestParameter constraint in the abstract EndpointService<TRequest> class.

Use attributes on the import class properties to define

1. Whether they are to be passed to the Dime.Scheduler pipeline
2. Which parameter name should be used

Instead of hard coding the property names, use these attributes to compose the import request.

Right now the URI must be constructed perfectly. The base URI must end with a / or otherwise, it won't work. Parse the incoming string and construct the URI.

Use AppointmentNo instead of AppointmentId.

Activate the license

Create a generic filter builder that generates Ext filter strings.
A fluent API would be a user-friendly solution.

string filter = Filter
.WithOperator(Operators.Eq)
.WithValue<bool>(true)
.WithProperty<Resource>(x => x.ExchangeIntegrationEnabled)
.Create();

The above pseudo-code should be capable of creating a filter string that can be parsed by the Ext filter framework:
[{ 'operator':'==','value':true,'property':'ExchangeIntegrationEnabled'}]

Would be a nice addition to the Dime.Scheduler .NET SDK. The same counts for sorters.

Create new users