Author: admin

I’ve been on the AWS train since day one. I’ve been integrating Amazon S3 and EC2 into my business(es) since they first launched a decade ago. While the platform has faithfully provided my storage and compute for over a decade, I’ve always been wary of vendor lock-in. After a decade-long ride on Microsoft (1998-2008), I felt pretty burned. Then, recently, after a similar decade-long ride on Google (2005-2015), I felt burned, but in a different way. After a decade on AWS, I’m nervous, but I don’t feel as burned; however, I’d say there is one aspect of doing business online that is making me put aside some of my concerns regarding vendor lock-in on AWS, and even on Google, and Azure–SECURITY. I’m just not convinced I can do this alone, and I need the help of the platforms I operate on to help make sure my operations are secure.

I spent the weekend setting up a set of APIs using AWS RDS as the backend database, AWS Lambda as the code layer, and AWS API Gateway as the API front-end. As part of this work, I established an identity and access management (IAM) role with policies tailored for brokering the exchanges between RDS, Lambda, and the API Gateway. I’m leaning on AWS for two key API security pieces here: 1) API key management with AWS API Gateway, and 2) backend security using AWS IAM. The key management stuff is pretty straightforward and something I can easily replicate, but the AWS IAM stuff is a little more involved, and I’m grateful for how easy AWS IAM makes it for me to setup roles, cherry pick from common policies, and lock down the infrastructure I a using to drive the backend of my APIs and other applications. https://goo.gl/wtgVpq #DataIntegration #ML

ICYMI: There are many reasons you want to have a roadmap for your API. It helps you communicate with your API community where you are going with your API. It also helps you have a plan in place for the future, which increases the chances you will be moving things forward in a predictable and stable way. When I’m reviewing an API I don’t see a public API roadmap available, I tend to give them a ding on the reliability and communication for their operations. One of the reasons we do APIs is to help us focus externally with our digital resources, which communication plays an important role, and when API providers aren’t communicating effectively with their community, there are almost always other issues right behind the scenes.

A road map for your API helps you plan, and think through how and what you will be releasing for the foreseeable future. Communicating this plan externally helps force you think about your roadmap in the context of your consumers. Having a roadmap, and successfully communicating about it via a blog, on Twitter, and other channels helps keep your API consumers in tune with what you doing. In my opinion, an API roadmap is an essential building block for all API providers, because it has direct value on the health of API operations, but because it also provides an external sign of the overall health of a platform. https://goo.gl/sEdFgA #DataIntegration #ML

Hi everyone,

On July 14th, 2017, the Brazilian government approved legal changes in the law No. 13.467/2017 in order to bring legislation into line with new labor relations. These changes became known as the Labor Reform and they come into effect on November of 2017.

The main impact of the Labor Reform for companies will happen in the process of payroll.

Are you curious to know what will be the aspects that will impact your work? The Labor Reform will cover several aspects of labor relations, but for the payroll process, what you need to know for now is quite simple.

Basically, your system will run with two main changes:

* Optional labor union contribution: Employees won’t pay labor contribution union by default anymore. With the Labor Reform, each employee will choose if she or he wants to contribute to labor unions or not.
* Termination by agreement: In this option, employer and employee make an agreement in which the notice period and the FGTS (Fundo de Garantia do Tempo de Serviço) value can be halved.

You will have the changes in your system in the next delivery phases. All details and recommendation will be described in the SAP Notes and in the documentation.

So, are you looking forward to the changes in the Labor Reform? We are ready to help you run according to this legal change!

Did you enjoy this post? Choose “Like” and share the content with your colleagues.

Feel free to leave your feedback, comment or question in the space provided below. And don’t forget to follow the tags HCM Payroll Brazil and HCM Payroll in SAP Community to stay tuned on HCM Brazil latest news.

All the best,

Leandro D’Avila
—

Olá, pessoal!

No dia 14 de julho de 2017, o governo brasileiro aprovou mudanças legais na lei n. 13.467/2017, a fim de adequar a legislação trabalhista às novas relações de trabalho. Essas mudanças ficaram conhecidas como a Reforma Trabalhista, que entra em vigor em novembro de 2017.

O principal impacto da Reforma Trabalhista para as empresas acontecerá no processo de folha de pagamento.

Você está curioso para saber quais mudanças impactarão o seu trabalho? A Reforma Trabalhista cobrirá diversos aspectos das relações de trabalho, mas para o processo de folha de pagamento, o que você precisa saber agora é bastante simples.

Basicamente, seu sistema irá operar com duas principais mudanças:

* Contribuição sindical opcional: Os empregados não pagarão contribuições sindicais por padrão. Com a Reforma Trabalhista, cada empregado poderá escolher se quer contribuir aos sindicatos de sua categoria ou não.
* Terminação por acordo: Nessa opção, empregador e empregado fazem um acordo em que o período de aviso prévio e o valor do saldo FGTS (Fundo de Garantia do Tempo de Serviço) podem ser diminuídos pela metade.

Você terá essas mudanças em seu sistema nas próximas fases de entrega. Todos os detalhes e recomendações estarão descritos nas SAP Notes e na documentação.

E aí, você está ansioso para as mudanças da Reforma Trabalhista? Nós estamos prontos para ajudá-lo a operar de acordo com essa mudança legal!

Gostou desse post? Dê um Like e compartilhe o conteúdo com seus colegas.

Fique à vontade para deixar um feedback, comentário ou pergunta no espaço abaixo. E não esqueça de seguir as tags HCM Payroll Brazil e HCM Payroll na SAP Community para ficar ligado nas últimas notícias sobre o HCM Brasil.

Um abraço,

Leandro D’Avila http://bit.ly/2hUoudO #SAP #SAPCloud #AI