Activities of "geertveenstra"

Hi,

I implemented the fix and now only the Payment Requests menu option is indeed visible. Thank you for investigating and providing the fix!

Here both are activated in the role (and both visible):

Here only Payment Requests is activated (but none are visible):

Hi,

Works perfectly! Thanks for your help again.

P.S. During the work I noticed an issue with the permissions: I have no need for the menu option "Payment plans" ( I need only the Payment Requests). So I tried to disable it in the Admin role, but if you disable the Payment Plan permission, then also the Payment Requests menu option is not visible anymore. Not really a big issue (for me), maybe it can be fixed in a future version.

Hi,

Thank you for the additional info. I did not have time to reply, but placing the index.js in Pages/Payment/Requests is what I already did yesterday after the AI reply :-) I also did a replacement of the Index.cshtml file for the Products lookup page (which also has some additional information in my integration).

Downloading the Payment module source code was unfortunately not possible for me (I guess it is not part of Team licence). Too bad, since I would actually also like to filter on the extra property, any chance to share the part where the filter is setup?

Thanks.

Hello,

I created a new custom gateway for the payments module and for the webhook function I needed an additional property to lookup the PaymentRequest based on the incoming payment reference id. For this I created an object extension and an EF extension mapping (because I need to look up the payment request record based on the extra property.

ObjectExtensionManager.Instance.Modules()
.ConfigurePayment(payment =>
{
    payment.ConfigureEntity("PaymentRequest", paymentrequest =>
    {
        paymentrequest.AddOrUpdateProperty<string>( //property type: string
               "PaymentReference", //property name
               property =>
               {
                   //validation rules
                   //property.Attributes.Add(new RequiredAttribute());
                   //property.Attributes.Add(new StringLengthAttribute(256) { MinimumLength = 5 });
                   //...other configurations for this property
               }
        );
    });
});

ObjectExtensionManager.Instance
             .MapEfCoreProperty<PaymentRequest, string>(
                 "PaymentReference",
                 (entityBuilder, propertyBuilder) =>
                 {
                     //propertyBuilder.HasMaxLength(128);
                 }
             );

This is all working fine, but what I am missing is the additional column in the Payment Requests datatable in the GUI. I did some additional object extensions (on the IdentityUser) and there all the properties are visible in the datatable.

Am I missing something ? Is it otherwise possible to override the entire page (get the sourcecode of this page) ?

Regards,

Geert Veenstra

Hi,

Thank you very much, exactly what I needed!

Hello, we have a client that needs to access our API and is requesting first an Access Token through OpenIddict (grant_type=client_credentials and client_id / secret). But the client is not able to request a specific scope (which to my understanding would be needed to secure the API with the [Authorize] attribute). Is it possible to return a defined scope in the access_token in the response? This is the current setup of the application for the access token:

The Authorize part is working when the selected scope is requested in the token request.

in local development (on localhost) calling app.UseAbpStudioLink(); seems to not work very well with stream-based grpc requests (like grpc reflection API for example)

the server is able to receive requests, but can't send back any response. I am guessing the middleware inserted by UseAbpStudioLink waits for the request to finish then sends the response, which contradicts how grpc streaming works.

This is blocking SignalR communication as well.

Error: Failed to start the transport 'ServerSentEvents': Error: EventSource failed to connect. The connection could not be found on the server, either the connection ID is not present on the server, or a proxy is refusing/buffering the connection. If you have multiple servers check that sticky sessions are enabled.