LogCore
Stable Version 1.2.2
Published on 15 September 2017 by 
Created on 04 September 2017
Details
The purpose of this component is to perform the audit log of the updated data in a given table record, which will consume the methods created in this component (SaveLogDelete and SaveLogInsertOrUpdate).
Read More

The purpose of this component is to perform the audit log of the updated data in a given table record, which will consume the methods created in this component (SaveLogDelete and SaveLogInsertOrUpdate).

What’s new (1.2.2)

Included logic to identify table name and primary key ID of the record being manipulated.

Reviews (0)
Category
Components, Libraries
Support Options
This component is not supported by OutSystems. You may use the discussion forums to leave suggestions or obtain best-effort support from the community, including from José Galter who created this component.
Dependencies
LogCore has no dependencies.
Requirements
Platform
10.0.0.402
Database
All
Stack
All
Component Consumers
LogCore has no consumers.
Weekly Downloads 
Related Components
Google Drive Connector
OutSystems R&D
Google Drive Connector allows your OutSystems Applications to use the Google Drive REST API to interact with your files.
1011
OutSystems UI Mobile
OutSystems R&D
Create amazing native mobile applications using this fully integrated UI framework for OutSystems, with dozens of UI patterns ready to use.
7375
Google Maps
Labs
Google Maps is a Google Maps Javascript V3 API component, providing Web Blocks and Actions to add interactive maps, markers and directions, along with event driven functionality.
10744
More from José Galter
Validate CPF or CNPJ
José Galter
Component is to validate the document number of a CPF or Brazilian CNPJ, indicates whether it is a document with valid or invalid syntax.
ConsultarCEP
José Galter
SeeCEP: Component built to consult address through the postcode, from the WEB Service made available FREE by the post office. https://apps.correios.com.br/SigepMasterJPA/AtendeClienteService/AtendeCliente?wsdl Geocode: Component also allows you to search Geocode - geographic coordinates of the CEP informed via Google Maps, and allows the developer to inform the Client's Google Maps API, so that the search via the client's account occurs. Changed the link to HTTPS because you need more trust requested on google. Limit of 2,500 free requests per day - 50 requests per second: https://developers.google.com/maps/documentation/geocoding/usage-limits#standard-usage-limits You must also create an Api Key for authentication through the steps in the link: https://developers.google.com/maps/documentation/geocoding/get-api-key Here is the documentation link for the google component used https://developers.google.com/maps/documentation/geocoding/intro#Geocoding